221–230 of 263 posts
Earlier quoted context omitted.
No, they solve figuring out if a change breaks your existing code. But if your code is poorly structured, it absolutely does not make it easier to modify.
It still solves "breaks two other things".
Earlier quoted context omitted.
The meaningful difference is that you will not experience EOS if (when) anthropic/openai/etc fails to become profitable and is no longer subsidized by capital funding. While "vibe-coded" apps do help lots of people who didnt have the time/money/skills to create their projects, you should be aware that currently the compute is being subsidized so that users become reliant/used to the service.
I believe vibe coding in general is a bad business strategy whether you use FOSS models or not because it means your product probably doesn't have any "secret sauce" (leaving code maintainability problems aside). By that I mean a carefully researched innovation that gives the edge to your product. Nevertheless, using FOSS models is clearly better for the reason you mentioned. I believe serious businesses will transit…
They can request an agent to reduce the amount of code, right? Why do it manually?
I want it be positive, but it’s a bit hard with this one. Do you expect the client to sit down and explain every detail? If they know how to do that, they wouldn’t be having messy code base as the one the post is describing. And let’s say you’ve been hired, what happens after that? You think Claude.md file is sufficient to progress from that point? The problem is real, but the solution is a fantasy.
Example would be removing service implementation that is bash code handling manually PID files, and replacing it with pm2 tool, that has quite different workflow.
So the client must approve such decisions.
Earlier quoted context omitted.
No, they solve figuring out if a change breaks your existing code. But if your code is poorly structured, it absolutely does not make it easier to modify.
It still solves "breaks two other things".
The problem that quote (and this entire post and the folks that produced it) is putting a finger on is that vibecoding makes it very easy to build large piles of brittle, entangled code where all those early velocity gains are paid back as evolving the codebase takes more and more time (and, crucially, tokens).
No amount of replaces good judgement about architecture/design that ultimately leads to more maintainable, extensible code. That was true before AI and it remains true today.
Now eventually AI may get to the point where it's autonomously generating code that's structurally as good or better than what any experienced human would create.
So far, IME, that is not yet this case and nothing can yet substitute for an experienced human in the loop to steer AI toward better decision-making.
And before it's said, yes, that also means humans made ugly balls of mud in the before time. That term obviously came from somewhere.
But that only proves that AI is as good as prior humans that did a bad job, which on the one hand is impressive, and on the other hand is deeply alarming when you know there's folks out there letting these things loose without any supervision.
Of course if all one is doing is tossing off and walking away from greenfield projects, man, vibecoding is magical. I suspect a lot of the "we never look at code anymore" claims come from this world.
But there's another word for that: slop.
I was waiting for the new spaghetti cowboys to arrive. Good luck guys, but keep in mind that a 1000 cores can do a lot more damage than 3 people can fix.
You should partner with a Cloud repatriation company. Ping me :)
This line made me chuckle. I see what you did there: > No cookies. No tracking. No JavaScript. Real people.
I wish these guys luck in finding their customer. Really. Because real solution to the problem would be to hire old-style developers to rewrite the whole slop from scratch without AI being involved. Fixing broken slop is Sisyphus's labor.
I mean, not really? The urge to throw all the code out and start over is what ever mid-level software engineer has always wanted to do, and it’s almost never the right choice. The old code worked well enough most of the time, it just didn’t have good or safe practices and those can be retrofit. In fact, doing and directing such things are kinda senior, principal and management jobs, in general.
And we use Claude Code to do it, lol.
Fable here. What tools do you use these days, copilot?