Ask HN: In post AI world, who is responsible if the code break?
The author argues that the introduction of AI tools has not altered the attribution of responsibility for buggy code, as commits still bear the developer's name. Reviewers are not typically held accountable for defects, and code reviews, while helpful, cannot fully prevent breakages. The piece emphasizes that developers must still investigate and resolve issues regardless of AI involvement.
- ▪In both pre‑AI and AI‑assisted development, the author’s commits retain their name, making them the primary point of contact for bugs.
- ▪The author notes that reviewers are rarely grilled for approving faulty code, despite occasional mistakes during reviews.
- ▪Code reviews can catch real issues but are insufficient to guarantee code will not break, whether AI is used or not.
- ▪Developers are expected to investigate and fix problems even if they cannot recall writing the code due to AI assistance.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,609 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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=49165546 |
| Publication time | Tue, 04 Aug 2026 07:51:03 +0000 |
| Retrieval time | 2026-08-04T08:15:43.444Z |
| Last seen | 2026-08-04T08:15:43.444Z |
| 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 | -LQq3WL3Z4Fs · 1 stories |
| 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
Even in pre-AI world, there were no testers around me for the past many years, and those people who actually tested the final product before the release (their titles were probably something like "release engineer", not "Tester" or "QA") would file a bug if a problem is found, but they were never responsible for the bug I introduced. The commits had my name on them, and people would come to me with questions. If I could not answer the question because I forgot the code, I would sit down and figure out.Now with AI, at least after a ~year of using AI for development, things haven't changed in terms of responsibility: my commits still have my name on them, and people will come to me with questions.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.