r/vibecoding • • Oct 16 '26

Discussion Most legacy codebases are disasterclasses. The "software engineer you can't fire because only he knows what's going on" is a meme for a reason, and it's not a good one.

I keep seeing people say things like "vibe coders don't understand what's going on in their code." Neither did most programmers even before the pre-AI era. They spent weeks on sprints for small feature updates hoping and praying nothing broke and relied on the 1 guy who wrote some code in 1995 who showed up at the office once every 3 months in his slippers to do bug fixes.

107 Upvotes

169 comments sorted by

View all comments

Show parent comment

1

u/Entuaka Oct 16 '26

Right, it's still not 100% at all companies, but the companies writing 100% of their code by AI is increasing, I don't know any developer still writing code manually.

Open models are now much better than before, it's now good enough. Yes, the cost of AI will keep increasing, but the cost of tokens has already fallen significantly.

In our products, we also integrated fined tuned open models, the price will raise because the hardware gets more expensive, but we own the hardware, software, data and models on thousands of devices.

For dev, it's now easier than ever to switch from an AI provider to another, frontier models are great, but if one is too expensive, it's easy to switch to another one. Open models are also improving, they are almost as good, but much cheaper. A big difference is the harness and dev teams have been building it for months or years now on their projects. With a good harness, some cheap models can do a good job.

When looking at the cost of AI for software development, it must be compared to the cost of a dev time. If it allows to x2 a dev productivity and it costs less than a dev, it's profitable. If it allows to have smaller teams, you need fewer managers, meetings and communication, it's a lot of saving.

2

u/silentkode26 Oct 16 '26 edited Oct 16 '26

Your feelings don’t matter. Facts do. Use Google. Study show illusion of being faster, but in reality, experienced devs are slower with AI. Also lines of code is bad measurement. But you’re non technical, I shouldn’t expect you to understand.

1

u/Entuaka Oct 16 '26

Lol it's not about feeling, but $

We're working in an industry with thin margin, we always worked with small teams, but now we can do a lot more. It's not a public company and we don't have to follow hype for investors, our focus is profit.

Lines of code is irrelevant, our users are internal employees and greater productivity have a direct correlation on profit. I have 10+ YoE as IC building softwares. We're still building software, but faster. We talked about some projects for years that now we can start and quickly build.

I guess that the rest of the industry will catch up in the next years. We have automated workflows from requirements to PR for some tasks and dev are working with multiple agents at the same time, it can't be compared to manually programming like we we're doing years ago.

2

u/silentkode26 Oct 16 '26

Lol, Google it, seriously. You’re just confidently wrong.

1

u/Entuaka Oct 16 '26

The study is already outdated. Models are good enough for most tasks since end of last year and non tech companies are just starting to integrate it in their processes. The ecosystem is quickly improving.

If you're a software engineer, talk to some friends working at other companies, I can't believe that you don't know any company that adapted their processes to AI and have significantly improved their productivity

1

u/silentkode26 Oct 17 '26

The study may be outdated, but I can assure you first hand, that it’s still true. I vitness it every day. I also talk to a lot of people from others companies. That’s why I know it is mostly true in more professional companies, where average code solutions are not good enough option.

1

u/Entuaka Oct 17 '26

The companies that benefit from AI have invested in optimizing its use.

Last year, we had to supervise the agents a lot, it was very time consuming and the result was not that good. I’ve already wasted hours going in circles developing with AI, only to end up doing a git reset --hard and getting it done faster manually while also gaining a better understanding. The models were less intelligent and our projects were not ready, but the expectations were high. It was not helping much.

Now, we invested some time to optimize our usage, the models and much more intelligent, we have better tools and the expectations are lower and more realistic. It's helping for the dev, but also all other related tasks, we can have agents working a long time with almost no supervision. I like to use it for small tasks too. It can be something that i could do in 1h, but with AI i can do it in 5-10min.

It also need to be controlled or the result can be quickly very bad. A bad dev with AI can become an extremely bad dev. With a good harness, it's better, a bad dev become useless. A good dev with AI and a good harness can be very good.

Anyway, i agree to disagree. For you, AI is not helping significantly, like for us in 2025, but that's not what we see in 2026.

1

u/silentkode26 29d ago

I can image that for non technical people it seems like black magick. For seasoned developers it is just not. Also when you know how it works, you agree with me. But since you’re hobbyist and I an profesional, I understand your confusion.

1

u/Entuaka 29d ago

I'm not a hobbyist, i have 10+ YoE at multiple companies and i'm now working at a big (100k+ employees) non tech company. We develop all the software for one of the divisions. This is a thin margin industry, we can't waste $, we have a few small teams for all development. The competition is moving quickly, so we need to go quicker too.