May 10, 2026
Vibes in, meltdown out
I'm going back to writing code by hand
After 7 months of AI magic, the messy breakup finally hit and the comments went wild
TLDR: The developer is scrapping his AI-built project and starting over by hand after realizing the code was fast to create but hard to control. Commenters turned it into a mini culture war, arguing over whether AI was the real problem, whether planning matters more, and whether the post itself sounded robot-made.
A programmer behind k10s, a dashboard for watching expensive computer clusters, has announced a full do-over after discovering the project had turned into a giant, fragile mess. The big confession? AI helped him build features at lightning speed, but when the app started falling apart, he finally read the code and found a monster file so bloated it basically ate the whole project alive. His verdict was brutal: AI can crank out shiny new parts, but it won’t save you from a bad blueprint.
And honestly, the comments are where this story gets delicious. Some readers nodded along like they’d just witnessed a public service announcement for the “move fast and panic later” era. One person basically translated the whole post as: maybe the real lesson is to plan better before letting the robot freestyle your project. Others were less sympathetic and way more chaotic, with one commenter dropping the gloriously reckless jab, “have another drink and drive yourself home,” turning “vibe coding” into a full-on meme about coding under the influence.
Then came the classic internet split-screen debate: was the problem AI, the programmer, or even the programming language? One commenter side-eyed the dramatic switch to Rust, asking if Go wasn’t supposed to be the easier option anyway. Another questioned the whole theatrical restart: why not just ask AI to clean up its own mess? And in the snarkiest twist, someone even said the post itself felt AI-written, which is about as 2026 as online drama gets.
Key Points
- •The author says k10s, a GPU-focused Kubernetes TUI dashboard, is being archived and rewritten from scratch after about seven months of AI-assisted development.
- •The project reached 234 commits over roughly 30 weekends and was built largely through prompting Claude to generate features.
- •Early development produced a working k9s-like interface with resource views, live updates, log streaming, command palette support, and keyboard navigation.
- •A GPU fleet view showing allocation, utilization, temperature, power draw, and memory was added as the tool's main differentiator.
- •After the fleet view was introduced, view switching and live updates broke, and the author traced the problem to a 1,690-line model.go file centered on a single oversized Model struct.