There is a quiet paradox inside engineering teams that have adopted AI coding agents at scale: we have never generated so many lines of code per minute, and at the same time, we have never accumulated so much accidental complexity so fast.
Ask a frontier LLM to implement a simple persistence layer for financial wallets in Go. Without strict architectural guardrails, in less than thirty seconds it will likely hand you:
A WalletRepository interface with a single concrete implementation in the producer package (violating the classic Go idiom where interfaces belong to the consumer);
An AbstractStorageFactory with a Strategy pattern for a database that will never change;
Three hallucinated domain structs ( CreditCard , VoucherBalance , WeeklyEnvelope ) that were already unified inside a single domain.Wallet entity;
A custom wrapper around database/sql and half a dozen vague // TODO: optimize later comments scattered along the way.
Does it compile?…