> “serious” documents with proper tracking of changes and so on are in Word
How does the tracking works in Word? I've never seen this proper setup so I'm just ignorant when it comes to this. If I hear "Word" and versioning in the same sentence, I'd just assume we're talking about the doc_v1_3_final_really_final_public_feb_2024.docx naming.
I gotta say, I found this one especially funny as I currently don't have a car and that's actually my biggest luxury: being able to go around without one and no spending time in commute.
As a passenger, I really notice the difference, and I wish more drivers (including professionals) would learn as you did. It probably saves energy as well, especially when driving in cities, although I guess it's marginal.
Back when I had a Prius, I made a conscious effort to avoid using the brake pedal during the highway portion of my commute. It made a small difference to fuel economy, but treating it as a game reduced the frustration with stop&go traffic.
I don't think it's marginal since accelerating the car needs way more energy than fighting loses due to wind and tyre resistance.
Also, a bad driver mis-breaking trips the cars behind into breaking too, which multiplies the energy waste and may also cause accidents through fatigue.
Mare experienced drivers will give you more leeway to avoid tapping the brakes with you, or simply go for a staring overtake.
I'm realizing I don't know if it's currently harder for an LLM to:
* come up with a formal proof that checks out according to a theorem prover
* come up with a classical proof that's valid at a high-level, with roughly the same correctness as human-written papers
This is even more relevant in the context of generated code, where most of the time is spent reviewing rather than writing the code. Abstractions, by allowing the code to be more concise, help.
With LLM code, I'd rather have higher-level abstractions.
As another commenter, I'm probably at 100s per day.
A reason is that I use i3 workspaces, with each workspace being for different tasks, so I don't want to reuse a terminal that has another context.
One issue with keeping a single shell is that the history is full of irrelevant stuff. If you run commands that take a while and print a lot of output, you want it to be as clean as possible. If I want the beginning of the command, I can scroll to the top, and I don't end up with some unrelated output.
I also take quite notes in vim everywhere, often next to long-running commands, using tmux.
I often write multi-line commands in my zsh shell, like while-loops. The nice thing is that I can readily put them in a script if needed.
I guess that somewhat breaks with fish: either you use bash -c '...' from the start, or you adopt the fish syntax, which means you need to convert again when you switch to a (bash) script.
I guess my workflow for this is more fragmented. Either I’m prototyping a script (and edit and test it directly) or just need throwaway loop (in which case fish is nicer).
I also don’t trust myself to not screw up anything more complex than running a command on Bash, without the guard rails of something like shellcheck!
I used to do it this way, but then having the mentally switch from the one to the other became too much of a hassle. Since I realized I only had basic needs, zsh with incremental history search and the like was good enough.
I don't care for mile-long prompts displaying everything under the sun, so zsh is plenty fast.
How does the tracking works in Word? I've never seen this proper setup so I'm just ignorant when it comes to this. If I hear "Word" and versioning in the same sentence, I'd just assume we're talking about the doc_v1_3_final_really_final_public_feb_2024.docx naming.