Hello programmers! I’ve been making a living for a couple of decades figuring out stuff for people and coding whatever will make them happy. It’s fun. I’ve grown to prefer the people to the coding but I still get a kick out of the whole thing.
The problem is: at the job we’re being asked to pivot to vibe coding. At this point the order is to use it for all code, read the slop carefully, argue with the machine for way too long and only then open that PR. Massive productivity gains are expected. I’m appalled from an ethical, philosophical and professional standpoint. We’re a non-profit ngo ffs. My colleagues are fine with it. If I get even slightly critical the group goes awkwardly silent and I get comments on how all the programmers they know from other places don’t code anymore.
If this is how it goes from now on, I’m out. Is it really though? Are all businesses switching to vibe coding? Have some of you started switching career? I think I want to go to meatspace. Hand-made coding could make a cute hobby.
Vibe coding means giving an LLM access to the entire repository and blindly accepting the very large pull requests it makes after you tell it what you want.
That is an insane way to do development and any company who does it will suffer.
What is becoming normal is AI assisted programming. The developer retains understanding of the codebase and uses an LLM to generate small boilerplate sections because it’s quicker than writing everything by hand.
Using LLMs to write code is perfectly acceptable as long as there is a human understands exactly what the code does. Do not give agency to the AI and you’ll be fine. Let it make decisions for you and you’ll be out of the job pretty quickly.
I am not a programmer, but related to a few. My cousin said his workplace actively evaluates people on token usage, where more is better. He has refined his prompts to burn as many tokens as possible.
Another relative said they only hire seniors now, and use AI for junior work. I told him there will be no more seniors in five years, doing things that way. Well, that’s a problem for later.
There are two things we measure inadequately with junior/senior. There are people who are highly skilled and have aptitude and passion for engineering - they are junior for lack of experience, but will be senior in good time.
Then there are people who are simply shit, who probably call themselves “coders”, who are proud of being self-taught by hacking out Javascript or got a vocational qualification from a Poly. They will remain junior forever (unless they work in outsourcing, in which case they’ll be billed as senior devs if they can bluff their way through for 6 months.)
The latter are fucked, the former will be fine; I suspect we’re going back to a world as it was 30 or 40 years ago though, where the quality of your degree is far more important and the number of vacancies far lower. I rather hope the death of outsourcing will also finally mean an end to the ridiculous job-title/expertise inflation that sector has wrought upon the industry.
I think I’ll use this answer to reflect. So first, vibe coding means, to me anyway, taking w/e the ai spits at you without checking/understanding. Aside from that, like okay, check the code send the PR. But anyway, at one point in my life, I thought, hey it would be great to go from writing code to reviewing code by others. I thought that would be a stepping stone for me. After a carefully thought, that’s what ai code gen is in the end. One of those careful what you wish for kind of thing.
I do think LLM is here to stay, one way or another. Might be like the next compiler like a comment suggested. I also do think that any software developer/engineer is stronger candidate with AI than one who rejects it.
Using AI codegen feels like returning to a beginner all over again. Throwing shit at a wall, begging the AI to cooperate, getting frustrated because nothing works and I can’t do anything to fix it because none of the code is mine.
I swear this was a phase I grew out of after years of dedicated practice. Now I’m forced back into it again.
I’m a full time code monkey. Last week I met a woman who created an on-line app. I asked her, “Oh, you must be a software engineer!” She laughed and said, no - she made it with Claude in about six months.
I felt a little deflated. This, the job I studied for, got a Masters degree in, working full time. It’s being supplanted by someone with no experience and an idea.
Of course, the site was buggy with UI issues, but it still stick in my craw a bit.
The job you studied for and got a masters degree in (congratulations, sincerely) was hollowed-out and deskilled years ago; it has been profoundly depressing watching the industry taken over by people who think a 6 month vocational course in Typescript and 6 months of not getting fired qualifies them as a senior engineer, with absolutely zero understanding of basics like information theory or concurrency mechanisms or, well, any basic engineering. These are the fuckers who have been producing spaghetti applications built on a MySQL (God burn its soul in hell) database with no relational integrity (“foreign keys make it slow!”) and no thought to scalability or resilience that someone else then gets to fix when the shit hits the fan.
That those people are going to be replaced with AI shouldn’t give anyone pause to weep. The arrival of AI to do their jobs is an opportunity to reverse the deskilling the industry has spent the last three decades working on - one really genuinely good engineer with an AI can now replace one really good engineer tearing her hair out at the half dozen absolute idiots she is asked to work with to deliver anything today.
AI codegen is dumb as fuck. It doesn’t understand system design at all.
I do use it to catch careless mistakes in nonformal connected parts of code though.
If you know what you’re doing and you know what good patterns look like then AI is a very good way to take some shortcuts and not have to write all the code yourself. It also keeps getting better. This is a super unpopular opinion on Lemmy, but I’ve been doing this job for 25 years and AI has only sped it up.
On the other end of vibe coding you have people who would never touch a compiler in their life if it wasn’t for AI, who are building practical, useful things in the real world. I think because Lemmy is so full of tech people that we often forget the tech serves larger purposes than just having nice code.
I think it’s also helpful to remember that short of an entire societal collapse we will never stop using these tools and they will only get better. The monolithic systems that are in place running the world are not going to change anytime soon. Even if we encounter a major correction of some sort these tools will only come back better and cheaper. You will never get everyone in the world to agree on regulation and at least one nation will march forward with progress unabated. You can hate the tech companies, the governments, the rich, the stupid, the right wing, the left wing, it doesn’t matter. We are locked on a course.
The price is also a big factor. They’re currently taking big losses, so your AI usage is being subsidized by investors. Eventually they’ll want a return on that investment, so the price is going to go up. Way up.
We don’t know yet whether AI is actually cost effective over just having a developer write the code. Or maybe it’ll be cost effective to use something on the level of Haiku for simpler stuff, and a human developer does the more complicated stuff.
I think it’s also helpful to remember that short of an entire societal collapse we will never stop using these tools and they will only get better.
I don’t think it will take a societal collapse to stop the use of these tools. Just someone at your company running a cost benefit analysis on it after the AI companies start charging the full price.
I was lucky to upgrade my GPU before the price increases, but the open weight models are quite alright for the moderate stuff, and electricity is much cheaper than the cloud token costs at the moment. So, unless HW prices will be forever high and that bleeds into the 2nd hand market too, I don’t think there will be at least some economical viability.
I am working in a very small company as a software dev and write everything by hand. I wrote some weeks ago in a different thread here that I tried all of the LLM powered coding tools and found all of them subpar.
If this company goes downhill or I lose the job otherwise, I will work something entirely different.
My very arrogant point of view is that these “vibecoding” tools are being celebrated by people who were making shit software before and now make software that is slightly less shit in what they perceive is the same amount of time, but I suspect it takes them actually longer. Meanwhile, they don’t grow their programming skills at all.
people who can suddenly “”“make”“” things like minecraft mods are also a part of those celebrating, though i assume they’re a lot less vocal about it
and god i wish that was all it was used for
From what I can observe, yeah, pretty much the entire industry has shifted to LLM code generation. I’m sure (or at least I hope) there are still some shops that go out of their way to keep working like we did, you know, months ago. But beyond that… I’m not even sure the general public understands how quickly and how fully LLM codegen has become the norm. It’s grim.
One question I have for the slop advocates in this thread is this - do you not like programming? Did you fall for the „learn to code“ meme and just learned the bare minimum to get a paycheque working on web dashboards?
Like why would you voluntarily cut out the most enjoyable part of the job, and go around scoffing at people who don’t want to do that?
Productivity is my boss’s problem, not mine, and I’d rather go and try and farm geese (I hate geese) than spend my whole day reading LLM generated code.
I love programming. I’m ok with others having access to programming that otherwise wouldn’t. I’m not having as much fun being a project manager instead. I don’t scoff at handwork coders. I’m also not going to pretend that they don’t code poorly without guidance. If you know coding you will be better at using them, but not significantly. I miss coding. I don’t understand quite why you are angry that I want to eat and provide for the family?
I don’t understand quite why you are angry that I want to eat and provide for the family?
Because it’s neither necessary nor morally neutral.
I use LLMs for code development, but I’ve found it’s only good for (a) boilerplate-level stuff I already know how to do and don’t want to deal with, or (b) VERY small tasks. Anything even moderately complex (at least by my opinion) blows LLM’s context budget and it instantly produces trash (any moderately comp-sci-interested highschool intern would write better code) that costs more time to analyze and fix than it would have taken to write it from scratch in the first place.
The responses to your question makes me fear for the future of products.
I use LLMs for scaffolding, boilerplate stuff, and basically things I can trust a junior with. For anything else, I have been forced to write it myself or rewrite it because the agents were so goddamn awful at it.
Reading that people even think programming has nothing to do with code and is just solving problems is just nuts to me. Code is a spec for a problem solution. If someone thinks the spec is neither important nor that being able to understand the spec is important… It’s like saying “I don’t care how this bridge is designed, it’s built”. Say that again and tell me it doesn’t sound nuts.
It explains a lot about the industry before the advent of LLMs. I always wondered why Node.js took over in web dev so quickly and that so many people only care about having something done makes sense. I just wish they weren’t destroying one of my few favourite things about humanity (Open Source Software) while they wallow in their own misery.
LLM won’t destroy OSS for me. It will actually be the only thing left to use because proprietary software will be the first place for LLMs to take over.
The problem with it is that it’s destroying the motivation of maintainers and causing projects to become closed to new contributors due to people not respecting contribution guidelines with agentic LLMs. It’s not necessarily destroying quality for those that have standards, but it is destroying the community.
That’s a good point. At the moment, I don’t have solutions besides not using the major Macroslop sourceforge, because they are heavily promoting the use of AI and knowing how they operate, it’s only going to get worse. Codeberg, Gitlab, Radicle, etc. might be temporarily safe until federation is implemented and another solution will have to be found.
There’s nothing to prevent you from writing code in an IDE while the torment nexus TUI churns out whatever monster misfeature request was waiting for you in your Jira queue this morning.
In fact I’d recommend doing the code writing part. It helps, even if it increasingly becomes a rounding error in your overall output.
It’s bleak as shit right now. God why couldn’t this have waited until after my retirement.
I’m far from a slop advocate, so this is more of a devil’s advocate point: plenty of code writing is not enjoyable.
If I’m working on my own project, to my own standards, writing exactly what I want to write I’m usually going to get enjoyment out of it. That’s pretty commonly not the case when writing code for an employer. Maybe the tech stack sucks, the product is inane or worse, you think the feature is a dumb idea but have to do it anyway, you’re bending over backwards to work around tech debt that you’re not allowed by management to fix, or you have to appease incompetent/out of touch architects or tech leads who presume to tell you how to do your job. I personally don’t enjoy writing that code very much. At a certain point it’s almost like nails on a chalkboard if you genuinely enjoy programming for its own sake: you know what good would look like, you know how far away what you’re working on is from good, and you feel sad at all the organizational inertia you’d need to overcome to get to good or, choosing not to do that, at compromising your standards. That bugs me, at least, and at a certain point makes it hard to even start certain work projects.
LLMs can make this at least bearable. Rather than spending hours looking into the change yourself, writing all of the code, fighting the shitty test framework and swearing at the past engineers who made it so bad, you let the robot figure it out and review its work. The result may still suck, but it was going to suck if you wrote it by hand too, for reasons largely out of your control. You can’t be fully hands off, and you still have to deal with the things you don’t like to get a good result, but you put yourself a step away from what bothers you and by doing so make it a little more pleasant. And, when you find work that’s actually fun, interesting, or rewarding, you just cherry pick that for yourself. I’ve grown to appreciate them for this reason. I have a lot less dread for the nails on a chalkboard work than I used to, anyway.
This is an interesting take. Thanks for sharing. I think this is a part of why many people avoid proprietary and corporate software.
When my AI fucks up code I sometimes think “I probably would have fucked that up too”. And then I make it write 50 more tests in 2 minutes so it doesn’t happen again. The ROI in time saving is too tantalizing for me to be a meat-only code monkey.
It does really need all those tests. But they probably should have existed anyway and I’m damn sure most devs out there weren’t going to be so obsessive with coverage.
I hate tdd. But this is what happened and now I am so glad they birthed that unholy methodology
I like to code. I like tools. There is a trap in using the LLM tool for everything. A Maslow’s hammer and everything looks like a nail type of trap.
Programming was never enjoyable to me.
Making things is. LLMs allow you to be extremely pragmatic and enjoy making things or troubleshooting things without tedious line by line nature.
Writing code was never “the job”, that is just the trivial typing part you do when the thinking and designing ends. The job is solving problems (which I enjoy very much thanks.)
This is like people who refuse to program in another language because they are “a .NET programmer”. That just tells me you’re a coder not an engineer. In my career I’ve been paid good money to write C51 assembler, C, C++, Tcl, Limbo, Java, C# and Rust (roughly in order) - LLMs are just what’s next.
I have written in hundreds of languages, but syntax is syntax. The job was writing code. That’s what we mean when we say “coding”. We dont mean “pressing keys”. We don’t mean “writing a romance novel”. This argument is empty as the robots suggestion pattern for your SaaS bl
If your job was writing code, and not designing solutions to solve problems, for which code was just the final expression - then I’m sorry, you do need to find a new career. Best of luck.
I do enjoy programming, but I prefer “getting stuff done”. While I enjoy programming, I’d rather just get it done and move on. I like the results of having programmed.
Productivity is my problem, because I build stuff for myself, not just for my boss.
If you work for a company that prioritizes profit over quality - yes.
I no longer work in government IT, but from what I have heard from old colleagues, quality is still prioritized there and they are not forced to vibe code.
I read a retrospective from another team yesterday. They were preparing a demo for leadership and apparently it didn’t go so well. There were many reasons like last minute changes in requirements but one line was interesting for this discussion: The use of the LLM agents caused confusion about who is fixing which bug and taking on which tasks. The agents act like they’re alone in the codebase and keep adding and changing code broadly whenever they see an opportunity for improvement. And that often without specifically being prompted to do so. Now if you have multiple team members collaborating on a project with each their agents, chaos ensues because the agents are not coordinating and the diffs/commits become insane and the team doesn’t fully understand them.
This actually results in a necessity to test more and longer because nobody knows which bugs have really been fixed now and rapidly preparing for a release or a demo becomes more difficult than before.
In my opinion an LLM can be very useful to rapidly prototype something. Especially with an API or language you’re not familiar with. But for Production it’s still a huge risk to push code you don’t understand.
Those engineers are bad
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.
Upvoted because I want it to be true
keep your skills sharp and persevere. we’ll get through this.
We’ll be the next generation that writes malware no one can stop
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.
Everyone downvoting you is doing it while sipping their cups of copium.
If they continue to ignore, then they’re gonna find out just how right you are. Real quick.
IMO until Astra the models were not good enough to really be worth bothering with, but we’ve reached a tipping point.
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?
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.
just less of them
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.
I’m a systems architect who uses agentic coding to get around some executive dysfunction challenges with writing my own code. I learned about the dysfunction late in life; maybe meds will eventually get me to a point where I can consistently work on a personal code project without a looming deadline or social contract in the loop. For now I am part of the problem. Hi!
I look at agentic coding as a firearms problem:
- it lowers the barrier to execution: anyone with sloppy aim can point and pull the trigger, and do a lot of harm in the process
- both perform better in the hands of people with discipline and experience, but that doesn’t change the fact that LLMs and guns have massively proliferated and any idiot can get their hands on one (or that shitty people benefit from mass producing them)
- the industrial complex producing guns profits from murder, and the industrial complex producing datacenters profit from murder of the environment and attempts to eliminate jobs
- the same countries who treat gun control as an anathema tend to view “AI” controls as an anathema
- analogies suck, they’re never perfect but they get the conversation started
That said, most of the people who hate LLMs also don’t know a damn thing about how they’re used correctly. It’s also not their fault. Sure, they’re under no obligation to be an expert about the thing that’s harming them. But there’s a bigger reason: the companies pushing this shit benefit from a world stage where people use them wastefully and inefficiently.
The short list of things most people don’t get:
Spoiler'd because most people also won't give a fuck.
- A LLM is like a ten year old with a doctorate who wants to impress you. It can answer random trivia off the top of its head, but it’s going to make shit up when it doesn’t know the answer.
- Never trust a LLM answer that was produced without a web search or web fetch. Pretend you’re that obnoxious algebra teacher who rolled their eyes at your calculator and told you to show the work during exams. Work for a LLM is tool calls: web searches and webpage fetches. Tell it to research documentation and best practices before you start. If you don’t, the answer you get will be dated by 1-2 years in the best case, and a confidently wrong hallucination at worst. (unfortunately you’re still at risk of being fucked because frontier labs use webpage summarization in these tool calls, and that summarization adds another vector for hallucinated shit; lovely)
- The baseline skills of the operator are more important than anyone gives credit. Your results scale to your own knowledge level and your use of the LLM to extend into adjacent subject matter. You’re also the one best equipped to notice when the LLM did something stupid, and the best one to refine the process so that there are fewer stupid outcomes. Employers don’t want to hear this: they want employees to go away. Frontier LLM labs don’t want employers to hear this: they need employers to buy into the delusion of eliminating their work force, and also financially benefit from people using the tools wastefully. (token burn = profit = the heat death of the universe as an afterthought, but that’s the next generation’s problem) Casual LLM critics don’t want to hear this: confidently incorrect echo chambers are the comfort food of anyone with an axe to grind about what they hate.
- Consistent results require controlling the probability space so that your pipeline swats the hand of the LLM when it’s lazy or generating slop. For coding, that means using languages or tooling that prevent major classes of problems to begin with (Rust, Go, Typescript) or toolchains that removed about sloppy code (pytest-ruff + pytest-ty for Python). It means extensive unit tests that cover expressions of functionality, and knowledge of how to prompt out bad behaviors. (don’t rewrite tests to conform to “preexisting bugs”, always align tests to higher standards, etc.)
I could add another ten bullet points here, but I’m not here to prove that LLMs are capable of being useful. I’m here to demonstrate that it requires knowledge of a problem domain to get the best results. That means you can’t get rid of employees familiar with the knowledge domain. You need senior employees to get the best results, and you need junior employees so that they can eventually become senior employees. Same as it ever was. But because we’ve got useless fucking politicians who are too busy lining their own pockets instead of, I don’t know, regulating a worldwide memory shortage caused by a handful of companies, the whole thing is cannibalization of human society all the way down.
We could have scaled this to operate in the consumer space at a fraction of the energy costs (Apple SOC style versus energy inefficient hyperscaling) and used it as something to generate value by augmenting the capabilities of individual workers instead of trying to replace them wholesale. It only makes sense that it should have benefitted everyone considering this tech was built on shoving libraries worth of human achievement into a training pipeline (often without permission), right?
Nah. They profit more if we don’t own our own compute and everyone is encouraged to burn energy on treating the LLMs like all-knowing oracles instead of research tooling. They control the access to creations built on stolen knowledge. But hey, if everything else gets burned down in the process at least they come out on the other side rich and bailed out.
Work at a saas company in silicon valley, pretty much all the code being written is from an LLM here. Everything is still reviewed by humans, and a bunch of rounds of LLM reviews as well though.
Productivity has gone up as far as I can tell, we are shipping more features with a smaller staff. Support cases also seem to be going down, at least ones that reach an engineer like me since a lot are being resolved earlier in the escalation chain by a support technician, or just the customer talking to the built in helper LLM in the product.
Our token spend is pretty high though, looking like I’m at $1,200 on the month so far, so there’s that but don’t hear to many complaints from the finance department yet…
I’m liking the transition, as I have less work now. My day is a lot more waiting on the AI to complete a task or waiting for a human reviewer to do a pass on the code so I can spend more of my time doing important things, like scrolling on lemmy.
As for the future, I don’t think this is going away as much as everyone else in this thread seems to be wish casting for that to happen. The coding agents and models are only getting better, and tokens will only get cheaper as the data centers come on line. Long term I’ve been looking into becoming an electrician, but for now the economics don’t make sense with my current salary, so sticking with it until they lay me off…
I’m liking the transition, as I have less work now. My day is a lot more waiting on the AI to complete a task or waiting for a human reviewer to do a pass on the code so I can spend more of my time doing important things, like scrolling on lemmy.
Maybe it’s just me but this sounds like torture to me. I have enough progress bars to wait for in my work day and I would rather do something else with my life if waiting and reviewing generated code becomes the bulk of it. It’s good to see that some people do seem to enjoy doing it so maybe there’s a chance I don’t have to.
This comment condensed all the thoughts and emotions of an entire episode of Black Mirror into a few paragraphs
I’m with you. Nearly same story, finance sector, east coast. It’s fun. It’s relaxing and I tinker with so many projects I never would have had the time for.
