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.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=48265976 |
| Publication time | Mon, 25 May 2026 12:17:09 +0000 |
| Retrieval time | 2026-05-25T12:37:36.725Z |
| Last seen | 2026-05-25T12:37:36.725Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | k0XRzWJCMqqn |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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.