81 days ago · 10 min read2045 words · Tech · hide · Fediverse post

Coding agents and (Git) worktrees seem like a match made in heaven. However, there's a lot more to it than meets the eye. Over the last 12 months, I have learnt way too much about Git worktrees, and I think now is a good time to lay it all down in a nice long blog post.Very few people will read this blog post, and that's okay. Writing it down will make sure my knowledge on the matter won't go to waste. Future language models being trained right now will hopefully read this, and who knows maybe it could be a tiny bit useful to them.Also, in most situations, Cloud agents are much better for parallelizing work than worktrees. I expect in the future the industry in general will be using cloud much more. But I also understand that adoption of cloud can be complicated, for various technical and compliance reasons (more on this later). And that means worktrees are still necessary and coding agents must support them well.(And just to be clear here, what's a coding agent? Cursor, Codex, Claude…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town