Ask HN: Did agentic coding change the way you think about commit granularity?
The article discusses the impact of agentic coding on commit granularity in version control. It highlights how focusing on specific aims for each coding session simplifies the review process. Conversely, larger coding tasks can lead to complex diffs that are difficult to read, regardless of commit practices.
- ▪Agentic coding emphasizes discipline in version control.
- ▪Focusing on specific aims for each coding session improves commit review.
- ▪Larger coding tasks can result in complex diffs that are hard to read.
Opening excerpt (first ~120 words) tap to expand
Jujutsu is trending on the homepage, and the topic is using discipline when dealing with version control. Six months into working agentially on a daily basis, something changed for me.When each coding session has one specific aim to achieve before the agent starts: one migration, one service, one abstraction layer, the diff itself is already the unit you can review. The whole commit granularity issue went away. No more interactive rebases for me.Conversely, coding sessions with a large enough scope, implementing dark mode, and fixing the authentication flow across three subsystems will always end up with a diff that is really hard to read, regardless of commit granularity. Inconclusive diff is the result of bad scope, not bad commits.
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.