What I Use

I've explained what this site uses here.

For writing code, I find that making minor code changes is easier in nvim, but I use Zed and VS Code for the most part. Zed has been the smoothest possible experience, also a lot more consistent when it comes to customising it. I cannot fully replace VS Code because Remote Tunnels is a must-have for my work. Believe me, I tried a lot with ssh and rsync before landing with Remote Tunnels, it's just way too convenient. In addition, here are the VS Code extensions that make my life easier:

• Better Comments
• Highlight on Copy
• TODO Tree
• Trailing Spaces

This list used to be much longer, but I've come to realise that reliance on these can largely be replace with usage of proper style guides. As an example, I used to use the Bracket Peek extension a lot; however, following practices like this will surely reduce the need for such tools.

That said, I use linters often (perhaps too often?) to introduce some consistency across projects. Here are the ones I found to work best:

• ruff for Python
• shellcheck as a CLI tool for shell scripts
• Most statically typed languages come with decent linting tools built in, (e.g., gopls for Go or zig-fmt for Zig); for C++ though, I use cpplint

I'm a big fan of CLI tools overall, but especially those with nice TUIs. These are some that saved me a lot of time in the past:

• rich as an alternative to cat
• tmux for both multiplexing as well as to persist sessions when using ssh
• lazydocker for a better overview of running containers
• bashtop as an alternative to top

I've been looking for tools to generate flamegraphs, and flamelens looks great for this; perhaps I'll write a post about my experience with it.