AI Weekly Malaysia

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: 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.

Ahmad Al-Dahle, who led generative AI at Meta and the Llama model launches from 2023-2025, joined Airbnb as CTO in January and is pushing it toward being an "AI-native company" via an "inside-out" approach: use AI internally to speed up product development, then apply the same capability to the guest experience. He cites self-reported numbers: 60% of Airbnb's code is now AI-authored, features and improvements shipped are up nearly 80% year over year, and average engineer pull-request throughput is up about 1.6x. The mechanism he describes is process, not tooling — product, design and engineering teams now move straight into shared prototypes instead of PRD-to-Figma-to-engineering handoffs, and an internal tool called Everest was used to accelerate the launch of a new external service. Note: the excerpt cuts off mid-sentence before details on the guest-facing deployment.

Why: The transferable claim here is organisational, not technical: Airbnb attributes ~80% more shipped features and ~1.6x PR throughput to collapsing the PRD → Figma → engineering handoff into one team working on a prototype, which is a change a small team can make this sprint without buying anything. Treat the 60% AI-authored code figure as a self-reported CTO number from a company with a ~$93B market cap, not an independently measured benchmark — useful as a directional target for your own AI-assisted workflow, not as a productivity guarantee to quote to your board.