The problem is not AI code, but not knowing about system architecture or intent
- ID
- 29444
- Status
- summarized
- Published
- 29 Sep 2026, 12:11 AM
- Fetched
- 29 Sep 2026, 2:53 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://www.ssp.sh/brain/the-problem-is-not-the-ai-code-but-nobody-knows-anything-anymore/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.5
- Created
- 29 Sep 2026, 2:54 AM
- Tags
- Audience
- developersvibe_codersai_agent_usersstartup_founders
What happened
In a 882-word post (created Sep 26, updated Sep 28, 2026), Simon Späti argues the real problem with AI-generated code is not code quality but that teams no longer know their system architecture or the intent behind past decisions. He quotes a developer half a month into a role at a big company saying specs, code, tests, PRDs, tickets and ticket resolutions are all made by Claude Code, that engineers from L1 to L7 do the same thing, and that people work 12-13 hours a day "just to press enter" while nobody reads anything. He also quotes Hoyt Emerson arguing data engineers are different because they had to learn the product and business from day one, and Sean Behan on product managers now being able to build what they want. The Hacker News thread drew 255 points and 169 comments.
Why it matters
The post's own framing is that AI lifts a below-average codebase up to average, so the thing you lose is not quality but the ability to answer "why is it built this way" — the quoted engineer's complaint is specifically that nobody gets time to read the code being shipped. If your team runs agents over tickets, decide now who owns architectural intent and require a short human-written rationale on non-trivial changes before merge; otherwise the first person to leave takes the only copy of the reasoning with them.
Discussion angle
The quoted developer says management's argument is that pushing code is no longer the bottleneck, yet the team works 12-13 hours a day — so what actually is the bottleneck in an agent-heavy team, and what would you measure to prove it? Ask the room whether anyone has a written record of why a system is architected the way it is, or whether it only lives in whoever prompted it.