Vibes Don't Maintain

Re:Vibes Don't Maintain by CrimsonCape on Thursday November 12, 2026 @04:47PM (#50474782)

The anecdote the author gave is already kind of outdated, since Claude will write tests and debug itself as it progresses. It doesn't take much insight to realize that the maintainers are going to be AI.

Houses are still standing built with hand saws and elementary-school level tools; we don't tear them down, just cut new pieces with power tools and bolt on new additions built with new pieces made from advanced tools.

Isn't AI just another purity test? nasty VSCode users instead of pure elite Vim users?

While the maintainers surely will be AI, the last bastion is the architects. Claude can write the scaffolding, but does Claude know how the parts go together? Even the concept of fuzz-testing existing means that even humans can't envision all the failure paths, so it would be unfair to hold the metric against AI. What we are going to see more of is the architectural failures: massive data breaches because the architecture aroung the breach will be reveaed to be laughably simple, from prompts that just didn't know what to ask.

[ Parent | on HN ]

Re:Vibes Don't Maintain by BubbleRings on Thursday November 12, 2026 @05:01PM (#50474950)

I wonder how big you could say my friend Larry's "context" memory is. He's the long-time architect of a big, complex, international micro-services based system.

I'm guessing that when he goes to debug a complex problem that spans across multiple systems for his app, he brain is paging through the equivalent of a well-written 3GiB markdown design document file.

And my opinion is, yes, pretty soon SOTAs will be able to be that guy, if we are willing to hand that much control to an AI. But I sure hope we don't--it seems like way too much power for an AI. However: Larry sitting next to Fable working together? A team like that could change the world. I hope he's digging in to Claude or something, I'll have to give him a call.

[ Parent | on HN ]

Re:Vibes Don't Maintain by my002 on Thursday November 12, 2026 @05:10PM (#50475040)

Agreed. Also, Claude could relatively easily add the features he lists as lacking (dark mode, translation, etc.). Responsive design is on by default now in most models. Stuff like logins/auth would be more complicated, but Claude could certainly do it -- it would make for heavier hosting dependency, though.

[ Parent | on HN ]

Re:Vibes Don't Maintain by orwin on Thursday November 12, 2026 @07:07PM (#50476310)

As long as claude don't use breakpoints skillfully enough to analyse weird behaviors, you will have to do some research yourself, sometimes. Especially in huge OOP codebase. Because print-based debugging can only get you so far until the context explode (and even then, honestly it's almost always faster to investigate yourself if your code if of high quality, which, i will admit, is becoming an issue lately)

[ Parent | on HN ]

Re:Vibes Don't Maintain by hn_throw2025 on Friday November 13, 2026 @05:14AM (#50481156)

I think the last bastion will be people prepared to take responsibility for a system and keep it running. And cast a critical eye to streamline and simplify. I use LLMs and they have a tendency to double down on complexity, rather than zoom out and ask “Why”.

Wherever there is a chain of command, the buck will always stop with a human. “Claude did it and I’m waiting for it to fix it, but it’s not getting anywhere” - this will not fly when there’s a severity 1 outage on something critical.

[ Parent | on HN ]

Re:Vibes Don't Maintain by imtringued on Friday November 13, 2026 @05:23AM (#50481283)

You're talking about AI on a blog about vibes? How about you post something more relevant for a start?

How is vibing the maintenance supposed to bring about anything different from the original vibed prompts?

[ Parent | on HN ]