They say that "history between commits" matters.
If it's really so for some people, a case could be made that their problems can already be half-solved by changing the granularity of their commits: just commit more often.
I disagree. JetBrains PyCharm has a similar "local history" feature that solves this very real and existing problem and has saved my ass more than once when accidentally overwriting changes before committing or fubar'ing a git reset.
1. Commits are really just manual checkpoints while you’re working. Why not automatically checkpoint everything so you can actually go back to an older implementation without needing to remember to commit it?
2. Agentic workflows are so deeply single player. It’s very annoying, I want to collaborate with my team with agents, not review the output of one dev’s agent which they’ll just shove back into their existing agent.
pknopf · · focus · HN ↗
lightbendover · · focus · HN ↗
TacticalCoder · · focus · HN ↗
If it's really so for some people, a case could be made that their problems can already be half-solved by changing the granularity of their commits: just commit more often.
eviks · · focus · HN ↗
insane_dreamer · · focus · HN ↗
anon7000 · · focus · HN ↗
1. Commits are really just manual checkpoints while you’re working. Why not automatically checkpoint everything so you can actually go back to an older implementation without needing to remember to commit it?
2. Agentic workflows are so deeply single player. It’s very annoying, I want to collaborate with my team with agents, not review the output of one dev’s agent which they’ll just shove back into their existing agent.