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.
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?
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.
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.
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.
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.
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 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.