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.

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.

At its Dev Day on Tuesday, OpenAI announced that Codex cloud development environments are becoming reusable and persistent rather than one-off remote sandboxes, accessible from a computer, a phone, or the cloud, with shared team settings and permissions. The refreshed Codex CLI adds voice-directed task start/control, a new /agents view for delegating and tracking multiple tasks, and improvements to prompt editing, session resuming, worktrees, and a cleaner terminal UI. Codex also moves into the ChatGPT desktop app as a code review surface that summarizes changes and can run automatic reviews before feedback is posted to GitHub pull requests or GitLab merge requests, alongside unspecified security and API enhancements.

Why: The persistent-environment change is the one with real consequences: if Codex environments carry approved settings and permissions and are shared across a team, then credentials, dependency versions, and network access now live in a long-lived workspace instead of dying with each task — so a small team needs a deliberate answer to who owns that config and what it can reach. Voice control plus the /agents view also means one person can supervise several parallel tasks from a phone, which changes how you scope work (smaller, independently verifiable units) rather than how many tools you install. Note the text gives no pricing, region availability, or Malaysia-specific detail, so treat rollout and access as unconfirmed.