122
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Sep 2026
122 points (96.9% liked)
Programming
28506 readers
1291 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
it's not gonna last. if you tune out of the hype and actually look at some hard data, vibecoding stops looking so hot: https://codemanship.wordpress.com/2026/08/12/ai-software-development-what-does-the-data-say/
the current token costs are unsustainable also. the only ones making bank right now are the shovel sellers: https://isaiprofitable.com/
personally i'm working on hand-rewriting several projects vibecoded out by a non-dev in a small shop. not only is a lot of this straight up broken nonsense, the amount of tech debt is staggering. previous job wasn't better, i had to spend more time fixing slop from former coworkers than actually introducing new features. keep your skills sharp and persevere. we'll get through this.
tl;dr: this, too, shall pass. but holy shit.
We’ll be the next generation that writes malware no one can stop
Upvoted because I want it to be true
But being able to ship small, mildly broken, internal tools for my non-technical coworkers quickly is actually amazing.
Nobody cares if the internal tool code is nice, but when it shaves 50% of the work off of sales the sales team gets excited. So if I vibe up a shitty UI it’s still a net gain.
I’ve probably automated away like 60% of the ad hoc work I used to get into internal tools, and that has helped a ton with workload and budget.
Careful. You know how it goes with temporary workarounds? Suddenly, you find yourself maintaining slightly broken load-bearing slop.
That’s a fair concern, usually I only vibe the UI.
I’m not a front end guy, so as long as I know the backends is good I’m fine with it.
Yeah, it's only the user's experience fucked over when the UI is sloped together.
Although I agree with you....
That's how the vast majority of software has been built for the past couple of decades. LLM's aren't different in that regard, just faster.
Ok, UI coding is messy either way.
I am a technician in the physics department for a major university. There are quick and dirty hardware hacks that I threw together 2 decades ago that are still in daily use. Quickly made mildly broken tools have a habit of lingering.
That's exactly how a webpage that displays an excel spreadsheet nicely in different tables, turned into a gigantic monster of a project that nobody fully understand at my workplace.
Well, kinda, because that was BEFORE ai. I can't even imagine what mockery of God himself they would have done with AI in their hands.
It's absolutely going to last. IMO until Astra the models were not good enough to really be worth bothering with, but we've reached a tipping point.
And while I still do read the code they make and then fix things (or tell them to do things differently), it's still waaaay quicker than doing it "by hand".
Sorry but if you're expecting this to be a temporary thing you're going to be very disappointed.
People said the same about older models.
Yep. Every. Single. One.
Yeah well they were wrong IMO.
I agree with you except for the Astra bit. The differences in day to day are marginal at best (compared to both Sol and Anthropic equivalents) and the paradigm shift came long before it.
I dunno about Sol but Anthropic models at least are waaay slower (at least x2) and also write that really annoying AI prose - it's not this, it's that, and so on. Astra doesn't do that, or at least not enough to be annoying.
Sol is pretty fast from my experience, but still does the same thing that everything before it did: generate plausible code that I need to correct (and often rewrite) afterwards.
I haven't used Astra yet, but I don't really expect it to change that. Once it becomes available at work, I'll give it a shot of course, but my expectations aren't very high.
Edit: turns out I have Astra at work. It meets my expectations. I've had to rewrite a bunch of test code it generated and point it to the docs for a library to show it that some methods were deprecated and soon to be removed.
It's copium, which is understandable. I think it's really important for people who want to have a reliable career in the industry 5+ years from now, to learn harness coding even if begrudgingly.
If vibe coding remains the norm and is actually sustainable, there won't be a reliable career. You'll be weavers being put out of work by the autoloom. You're worthless to them. What can you do that someone with six weeks (or less) of training can't?
AI seems to be killing opportunities for entry level engineers. Hiring and interviewing processes I've been involved with or observed in the last ~2 years have greatly favored experienced engineers, just less of them. I'm gonna do my damndest to adapt, network, and remain in that bracket.
That's not a trivial problem. There will still be some programmers, but everyone will be competing for a shrinking number of jobs.
That's not a future with a stable career. That's a future where you're going to have to fight for the rest of your life to keep a job.
Unless the LLM hype craze dies down and they realize "oh actually we can't replace people yet" and they start hiring again.
You know the current state of IT security? It's bad.
Aand here comes AI. It will not make it better, even though it finds some issues faster.