Bad Code Is Kudzu
Summary
The article compares bad code to invasive kudzu, emphasizing the need to proactively remove features from codebases to manage complexity, especially with AI-generated code, illustrated by the author's experience deleting an unused hashtag feature.
View Cached Full Text
Cached at: 09/13/26, 11:41 PM
Similar Articles
@mattpocockuk: In a phrase, "make bad code unrepresentable"
Matt Pocock argues that in the AI coding era, developers should embrace more abstractions combined with strict lint rules to constrain AI agents to making only good design decisions.
Maybe We Shouldn't Be Reviewing All This Code
The article argues that code review is often used to solve the wrong problems, suggesting that feedback should be shifted left through practices like pair programming and team design sessions, especially with AI increasing code output.
@kentcdodds: I used Fable and Grok 4.5 (in two separate chats) to go find all the hilariously bad AI-generated code in my codebase a…
The author recounts using Fable and Grok 4.5 to identify and remove poor AI-generated code from their codebase.
When I reject AI code even if it works
The author explains why they often reject AI-generated code even when it works, citing reasons like inability to explain the approach, overly large diffs, premature abstractions, and reduced system reasoning, and argues for mandatory human review.
"Do You Still Read the Code?"
This blog post explores two AI-augmented coding approaches—accelerators who maintain code understanding and vibecoders who delegate more to AI—and discusses their long-term implications for software maintenance and team dynamics.