A software developer documents losing coding ability after a year of pure vibe-coding, now relearning by hand and resisting the urge to outsource even this blog post to Claude.
Key Takeaways
Author stopped writing code entirely for 1-2 years, prompting only, and has mostly forgotten how to code – now deliberately relearning by hand.
AI-generated writing fails the author’s own voice test: it doesn’t sound like him, doesn’t say what he wants, reads as obviously AI.
Imposter syndrome and self-doubt are the psychological lever AI dependency exploits – the author nearly pasted this post into Claude before catching himself.
Author predicts AI will shrink but not eliminate demand for developers who can actually read and write code, echoing Uncle Bob’s argument for returning to engineering professionalism.
Hacker News Comment Review
Experienced developers report a retention gap: features built with Claude are understood and recalled less deeply than self-implemented ones, consistent with pedagogy research on effortful learning.
A recurring practical warning: Claude defaults to adding code rather than removing it, producing growing codebases that asymptotically approach 100% debt unless every output is closely reviewed.
Commenters split on the core fix – some maintain skills via code katas and deliberate hand-coding; others have mentally reframed their role as spec-writing and AI-output judgment rather than line-by-line authorship.
Notable Comments
@gavinh: Reports measurably worse recall of AI-assisted features days later, and is now experimenting with active code-review exercises to compensate.
@ryandrake: “your codebase is going to just grow and grow, and asymptotically approach 100% debt” – estimates 90-95% of Claude output works but still requires full review.
