Compared to Zed Agent, Claude Code is: - Better at editing files. Zed would sometimes return the file content in the chatbox instead of updating it. Zed Agent also inserted a new function in the middle of the existing function. - Better at running tests/compiling. Zed struggled with nix environment and I don't remember it going to the update code -> run code -> update code feedback loop.

With this you can leave Claude Code alone for a few minutes, check back and give additional instructions. With Zed Agent it was more of a constantly monitoring / copy pasting and manually verifying everything.

*I haven't tested many of the other tools mentioned here, this is mostly my experience with Zed and copy/pasting code to AI.

I plan to test other tools when my Claude Code subscription expires next month.

Now I'm testing Claude Code’s $100 Max plan. It feels like magic - editing code and fixing compile errors until it builds. The downside is I’m reviewing the code a lot less since I just let the agent run.

So far, I’ve only tried it on vibe coding game development, where every model I’ve tested struggles. It says “I rewrote X to be more robust and fixed the bug you mentioned,” yet the bug still remains.

I suspect it will work better for backend web development I do for work: write a failing unit test, then ask the agent to implement the feature and make the test pass.

Also, give Zed’s Edit Predictions a try. When refactoring, I often just keep hitting Tab to accept suggestions throughout the file.

[1] https://waitbutwhy.com/2016/10/100-blocks-day.html

[1] https://99percentinvisible.org/episode/the-laff-box/

My hand gets tired if I use mouse too much especially with dragging operations. Using TWM and modal text editor helps a lot.

I really miss it on macos when I have lots of stuff open and have to switch between multiple windows. I haven't yet tried any tiling apps on mac because configuring is always a deep rabbit hole. I use Rectangle but having more than 1 window on a 13" screen isn't that useful and still requires manual arranging. A better control over workspaces is what I miss.

With so many servers Ansible script would ocassionally fail on some servers (weird bugs, network issues, ...). Since the operations weren't always atomic we couldn't just re-run the script. it required fixing things manually.

Thanks to this and emergency patches/fixes on individual servers, we ended up with slightly different setup on the servers. This made debugging and upgrading a nightmare. Can this bug happen on all the server or just this one because it has a different minor version of package 'x'?

We switched to NixOS. It had a steep learning curve for us, with lots of doubts if this was the right decision. Converting all the servers to NixOS was a huge 2-year task.

Having all the servers running same configuration that is commited to GitHub, fully reproducable and tested in CI, on top of automatic updates of the servers done with GitHub action, was worth all the troubles we had with learning NixOS.

This entire blog post could be a NixOS config.

[1] https://waitbutwhy.com/2016/10/100-blocks-day.html [2] https://github.com/am-on/work-timer

I'm working on a personal dashboard for the screen. I'll create a website in React and then use rendertron[2] to get the screenshot on the Inkplate.

[1] https://inkplate.io/ [2] https://github.com/GoogleChrome/rendertron