AI Weekly Malaysia

In a Sep 26, 2026 post, Alex Ewerlöf argues that "coding is solved" is wrong, claiming that maintenance, reliability, security and scalability (non-functional requirements) — not initial code creation — make up most of the cost of real software, and that even functional requirements remain unsolved. He names only three cases where not reading the generated code is defensible: personal software, proofs of concept, and deliberately weaponized AI, and contrasts them with low-risk-tolerance domains like healthcare, finance, automotive, defense, power plants, aviation and manufacturing. The piece drew 215 points and 204 comments on Hacker News.

Why: If your team uses LLM coding tools, this gives you a usable triage rule rather than a vibe: the author's own line is that skipping code review is only defensible where risk tolerance is high (personal automation, a throwaway POC), while anything where a mistake costs money, lives or legal exposure requires a human who can be held accountable — which he argues an AI structurally cannot be. The practical decision is which of your shipped features sit on each side of that line, not whether to adopt the tools.

Cal Newport's September 28 essay argues the two leading frontier AI labs spent months running a coordinated campaign — OpenAI announcements and reports about its 'felonious' LLM-powered agent systems, Anthropic researchers publicly debating the probability their work leads to human extinction, and Dario Amodei's letter 'We Must Pace the Frontier,' which Sam Altman publicly endorsed — that backfired into public suspicion rather than admiration. Newport contends that Amodei's letter, which enumerates harms his own company's research might cause and concludes the fix is government slowing potential competitors while the labs lead, is exactly the kind of behavior that warrants investigation. The Hacker News thread drew 235 points and 77 comments.

Why: The concrete, checkable claim here is regulatory capture: Amodei's letter asks government to slow potential competitors while the labs advance, and Altman backed it publicly. If your roadmap depends on a single frontier model API, that is a reason to weigh provider concentration and release-cadence risk instead of assuming open competition continues. The piece introduces no new technical facts, so it should not change any code, model choice, or migration this week — and it contains no Malaysia or Southeast Asia angle.