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.
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
Fair point. I skip lockfiles, changelogs, and generated code. The first application file on the list is the one that matters. Should have been explicit about that in the post.
Only two of the five depend on commit messages. Churn, authorship, and velocity work regardless. Even teams with terrible hygiene write "fix" when something breaks.
Big projects tend to self-correct. These commands hit differently on private codebases with 3-10 contributors, where high-churn usually means one person patching the same thing repeatedly.
One of the things I tried really hard to do is make the HTML _really_ clean for things like this.
Is reader mode "really good" or do you think it loads very nicely because of the work we put in to make the HTML nice?