Yeah! Worktrees were already sitting there. Agents just turned them from an occasional convenience into something I use every day.

Love it! Same here. bin/ is a convention I picked up from Rails and thoughtbot over the years. I also have bin/staging and bin/prod for data fixes, deploy helpers, and querying the DB, alongside bin/test and bin/dev.

Yeah, I've used bin/ and scripts/ in the past as well as _scripts/ ... but I just like the ergonomics of run/foo... run/api, run/ui, run/api-test, ... etc.

I'm usually working in a subproject, so it's usually ../../run/foo in practice, but still.

Yeah! All the same. I love this pattern.

Author here. Parallel worktrees showed me where Git’s isolation ends. Files stayed separate; ports, databases, cache keys, queues, and Compose resources did not. We now share compatible services and isolate names per worktree. Which shared resource has been hardest for your team to isolate, and why?

Did you write your post with AI? It is really painful to read in some parts (mostly because of the cliches of AI)

Actually no, sat down and wrote it out. Did some AI proofreading but applied the suggestions by hand. Would be interested to hear what parts were painful.

I audit engineering teams for a living and see this constantly: a 6 person team running ceremonies lifted from whatever 400 person org the founders came from, and nobody can say what coordination problem any of it solves. Adding a process is easy, killing one is somehow a whole political project.

Lol! I was baited into clicking this one. Cute title

This is pretty cool, thanks for sharing. It really enables less tech savvy users. It would really enable frontpage/dreamworks-like flows for some people

This is so sick!

If you use arch but you are forced to be on a mac for any reason, this will make you hate yourself less.

Wrapping these in a TUI is on my list. Haven't built it yet.

Good catch. The word boundary syntax isn't portable across platforms. I reverted to the simpler version that works everywhere.