grepsedawk

Yeah! All the same. I love this pattern.

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.

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.

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?

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!