bacon

I keep htop and some vim buffers open regularly, and I keep some tools open while a work on a project e.g. https://github.com/Canop/bacon. But everything else is opened as needed. Especially toys like this weather thing. EDIT - I use a 4k monitor and the window manager niri, so it's easy to fit multiple terminals on a screen

bacon is the superset of this with multiple types of custom jobs and job supervision supported. Although setup for Rust OOTB, it's easy to change it to be used for anything else and change key mappings. https://github.com/Canop/bacon

Rust is my main programming language and Python the second. Rust is very much useful for application programming - especially these sort of applications. In fact, Rust is the language I sometimes reach for when my shell scripts cross a certain threshold of complexity. Rust even has some tools and an RFC to address the use case of using it like a scripting language (I believe that Go has something similar too). I don't face much friction from the borrow checker to consider it a 'heavy price for not having a garbage collector'. There are even tools like bacon [1] that can give your real-time feedback on your code. It's even better with the default language server. I sometimes train other developers in Rust - mostly people who are not even into systems programming (JS, Python programmers). However, they don't seem to struggle too much with t

> jj makes it super easy to "fix up" your commit tree to what you want it to look like. I hit this today in a fun way. I was working along as one does, and needed to write a parser for a simple s-expression based language. So I did that fairly quickly, added a few tests which appeared to pass, and kept on working. A few commits later I reached a point where I needed to manually test my code. And promptly hit a stack overflow in the parser. A few minutes of debugging I understood the issue (I'd used the wrong function and failed to require brackets around a nested s-expression) - except I could have sworn my tests should catch it. So I ran my tests manually, and lo and behold they did catch it. Turns out that there was a bug in the tool I was using to run my tests [1] that was masking the test failure. I had completely broken my tests for

Every job I've worked in has had CI that is in some way unsatisfactory for me personally. But, I tend to work on projects with lots of configurations and tests that I want to run. So, I made Limmat as a way to get want I want out of the CI as a developer (which is often a bit different from what is needed from the CI for project health, and always different from what the CI infrastructure is capable of delivering). It started as an exercise to get used to Rust, but it turned into a pretty valuable part of my workflow. Basically it adds a new point on the spectrum of <things that run tests>. It's more lightweight and easier to configure than CI, but it supports a more rigrous workflow than stuff like Bacon that just optimises for fast feedback. [1] https://github.com/Canop/bacon

You may also find https://github.com/Canop/bacon to complement this type of workflow / mental mode. I keep both bacon and cargo-watch installed and use each regularly but I probably spend more time with bacon for commonplace working sessions. Also in the ring are https://github.com/eradman/entr and watchexec (which shares code and authorship with cargo-watch IIRC). As you can see I'm a fan of changed-files-automatically-do-things workflows.

Probably one of the biggest speed ups to your inner loop writing / running code is to use something like https://github.com/Canop/bacon/. I used a combination of the docs and GPT chats to increase my learning speed a lot.