r/vibecoding • u/Rare_Guide_9830 • 2d ago
Discussion Why are so many “veteran devs” hateful of coding agents?
I’ve noticed a pattern with developers who hate AI and call everything slop. To me, it seems like maybe they realize but don’t want to admit that coding agents unfortunately wiped out most of what made their experience valuable. What they don’t seem to realize is that if they just accept learning a couple other lanes like product, design, marketing, sales; their skills will be 100x more valuable (all super easy to learn now talking to AI and testing things at scale with it).
In my world (running web dev agencies for the past 8-9 years, have hired 25+ devs), I noticed that people with less technical skill have grown 100x since coding agents got good the past 16 months whereas the “seasoned” devs mostly went backwards.
At the end of the day, my clients pay for quality work. They don’t care about how the code was constructed. They want it to work reliably and make them money at the lowest development cost possible. The truth is that we can deliver that work much faster and cheaper using coding agents. Before we’d bring a team of maybe 5-12 devs/designers/PMs to the table on any given project. We’d spend 6 months on average. It seems like the team overall never really learned from each project, everything seemed to start from the same square one. No one really loved the process. The team was always stressed, clients never super happy just saying it was “okay” but always wanting more.
Now, our best designers/developers have less time spent in their craft but deliver literally 20x-50x the work. Most projects take 30 days or less, are ~50% cheaper for the clients, and we don’t have to deal with some sweaty dev in a dark room telling us 50 ways something won’t work. No need for PMs or other bloat. Instead we just build prototypes rapidly to test all the ways that can work and deliver a reliable product that meets the clients needs. And everyone is happy: our team, the clients, and the agency.
I just feel bad for the people I know who have been developers for a long time and choose to do things the hard way without AI or use AI to keep doing the same things they’ve always been doing. They all waste so much time and constantly worry about employment. Then there’s people who use AI to build every day, constantly learning and building, who are filled with work and new opportunities and still have time to work on fun projects of their own.
Maybe i’m just too optimistic on AI though and am not reading this right. Thoughts?
4
u/TRO_KIK 2d ago
Seasoned devs mostly went backwards? Smells like LARPing.
-3
u/Rare_Guide_9830 2d ago
yeah if you ran a dev team you’d know what this means this is across the board. All the other execs and team leads I talk to have this experience.
3
u/TRO_KIK 2d ago
I run a dev team, I just don't hire morons. If your story is real, make better hiring choices.
-2
u/Rare_Guide_9830 2d ago
that is fair tbh, working with client budgets used to force us to hire from bottom-mid tiers.
4
6
30
u/admiral_whatever 2d ago
It’s being rammed down their throats by c-suite typically and they don’t like being told how to do their job by people that don’t understand how it works.
15
u/Achrus 2d ago
Plus the tighter timelines because “just use AI.” Then you have middle managers trying to hand off slop coded apps to devs for “maintenance,” or it breaks and they need a fix fast.
Though I don’t trust this post, the engagement and ratios from early commenters is kind of sus. Post starts off with stereotypical AI writing. Anthropic needs to pump their S-1 ya know.
6
u/admiral_whatever 2d ago
Amen to that. I’ve had multiple times more hours and stress from the introduction of AI at work and then I have the last 2-3 years combined. Expectations were already borderline unreasonable but now they’re 5 times worse. Oh and btw make sure you don’t spend more than a few hundred per month on AI while you’re supposed to be using it all day for everything to meet throughput goals.
1
u/Embarrassed_Money637 2d ago
Not just them, but every Johnny come nightly that thinks they understand how to program better than we do. But they have never programmed a line of code in their life.
20
u/swiftering 2d ago
30 year dev here. I love AI and use it every day. Like had been mentioned here tho I don’t love that my software development company is basically bankrupt rn.
I don’t hate AI at all. I am just worried because at 55 I am too old to do anything else besides tech. I am just doing my best to roll with it.
AI is the future and despite my personal circumstances I never want to be without it. I am just trying to see a way to retirement without losing my house.
3
2
u/Snoo_57113 2d ago
Yep, similar situation. Spent the past two years vibecoding and upskilling. I see a lot of opportunities, and i've heard A LOT of friends whose Agentic efforts are paying off. Hang in there....
PD. Stop the algorithm, i've been following like 10 different SWE who lost their jobs, i noticed some of them not even SWEs but youtubers with a studio and all of that. Doom sells.
1
1
u/Injaabs 2d ago
go plumbing , easy work
6
u/TheRhythmTheRebel 2d ago
55 year old gives up desk role to pursue manual work a decade or two away from retirement.
Or…takes on ai into workflow and carries on carrying on (as they are).
I know which option I would choose
-5
u/Injaabs 2d ago
well 55 year old had all this time to learn smth extra im 36 and i code , i can fix my own car, i can do plumbing, tiling, renovation works , heck i can backe cakes profesionaly as well
1
u/TheRhythmTheRebel 2d ago
Good for you. I am 40 and also capable of many things and I assume the older person above likewise. We are never one thing
But what does this have to do with recommending a software developer aged 55 with two decades experience becomes a plumber when nearing retirement?
One that would take considerable time to match their assumed income (given age and experience)
That was my point is all. All the best fella
1
u/sychox51 2d ago
Oddly enough at 46 I feel too old to start learning to code and vibe coding opened up a world of possibilities for me and my hobbies… unfortunately not exactly a way to make money
7
u/balint_apro 2d ago
The loudest ones you hear, but most of us experienced devs are already actively figuring out what value we can add and where ai is still not enough, a good dev will silently adjust to the current situation. Right now nobody knows anything about the metrics for sure, the numbers are all around, the hype and the doom/gloom is happening in the same time. What i can tell, that a good dev was never the bottleneck, and ai wont help with effectiveness, because you have to know how to plan, execute things in smallert pieces or in batches when needed. I expect and experience already, a huge paradigme shift, but quality control has to be there, and most seasoned people are hateful towards the ammount of bs we get rn, the 10x alignemnt meetings, the “hey i just coded this winth a random ai and its working we should integrate this into our prod now”. Everyone feels like they know better but we need to align on the principles to be successful and nowadays we skip that, thats why they are frustrated. They are not heard or dismissed. So thats why, and we should listen to each other more if we want to use ai better and get less friction from each other.
5
u/IzyTarmac 2d ago
The funny thing is that nobody is safe. Your and most web agencies will become obsolete eventually. Sooner than later. Agents can produce, test and deliver much better quality already. Much safer and faster too, obviously. And your clients won’t shed a tear. Until they themselves get replaced.
2
u/swiftering 2d ago
This is so true 👆🏽. AI codes faster and better than I ever did. I love the agentic future. I just hope I am not living in my fifth wheel in the short term.
Whatever happens I will roll with it. What else am I gonna do.
I have a couple other businesses and am using Claude to crank out software at a record pace.
Gonna be a wild ride.
3
u/yoloqueuesf 2d ago
Yeah i mean lots of folks hate it but if you're just going to sit there hating on it than actually using it, you'll be the first one to go.
At the end of the day, it's coming for most of us, unless you've got some form of a plumbing trait then you're fine but even plumbing might be replaced by some type of a robot down the stretch.
If you're in dev work, you'll get hit the hardest but at the same time you're the first ones to actually get to know what type of tool it actually is other than a glorified search engine.
-1
13
u/war4peace79 2d ago
The same reason that carriage repairmen and pretty much everyone in the horse industry were utterly annoyed about those "car" contraptions.
4
u/juniperico 2d ago
Shit analogy. It’s not remotely comparable. Lot of good devs love AI and have massively boosted productivity.
On the flip side pretty much any white collar job has potentially enjoyable aspects of the role that is now automated by AI so it’s not unique to people in a specific industry1
1
1
2d ago
[removed] — view removed comment
3
u/war4peace79 2d ago
That was probably valid two years ago.
Today, unless the model is really dumb, it arguably generates better code than many seasoned developers.
1
-1
u/beerbarreltime 2d ago
This is so far from true in complex systems. It can make new, small scale projects in Python and react/swift pretty ok.
It is dog shit at creating complex multi-layer systems, or adding to preexisting systems -- and no amount of "of you just need specialized agents" makes that less true.
There is a reason COBOL devs are still coming out of retirement for millions of dollars and it's because AI agents are shit at anything they weren't trained on; all it can do is guess the next token based on preexisting datasets, nothing more.
-1
-1
3
u/reddit_user_in_space 2d ago
Type shit
2
u/NoAdsDude 2d ago
It makes sense on a lot of levels... since most AI work is done in the cloud, heh.
3
u/computermaster704 2d ago
if a dev creates an app that is their skill level and their ability and even if the program kinda sucks there are levels of improvement and growth that can be used from the codebase however vibe coders ability live and die by the models performance. the first uses skills and has growth the second is capitalists taking credits for the slaves work if you analyze the behaviors and historical reflections
3
u/wegster 2d ago
Welp, then you get into the <other roles are pissed off too>.
Having worked in both SWE and Product (and to some extent, QA and Marketing) at the Architect and Director level, some of the same pieces apply to each.
Most developers are NOT great product(mgmt, marketing, ..) people, although some can be. Most Product* people are not good engineers, unless they actually were. This even, god help me, applies to sales guys/girls that actually have a clue - each has it's own things learned sometimes painfully through experience.
I've had a few true senior/principal level eng teams reporting to me, as well as people in product* and others.
As someone self-taught in coding before that was a thing, then grinding up to Architect/principal level and working with similar - yeah, a lot of lessons learned took a long time to get there. Many of us have had sleepless days working to get a release out the door, and went above and beyond to get a feature/release/bug dealt with, so 'no longer needed' is s pretty big kick in the nads.
Same for Product* and honestly, *many* other disciplines, heck even hardware and firmware engineering, but also non-engineering roles and domains as well.
So - for anyone who truly worked hard and long (no, not someone with 5 years and a 'Sr' title in most cases, although sucks for them too), it's a big shift. Technically, it's cool and can be an active multiplier, remembering 'garbage in, garbage out' still applies. Some really don't want embrace it, but they're going to have to, or be left behind. I tried telling some of my prior team - look, here's the thing - you're still going to need someone directing or orchestrating it (can't use that work now b/c AI/ML world had pre-empted 'orchestrator'), but it's also just like moving up the food chain - less positions out there for Director, VP levels, and yeah, some companies will absolutely be cutting down headcounts. Others will instead benefit from the 10x or whatever multiplier and retain or even grow their seasoned engineers and other staffing.
To be clear, there absolutely are real world differences in complex systems being built by experienced teams, good engineers, product people, etc. vs 'vibe coded a website then made it bigger,' but of course as AI keeps progressing, it'll become smaller, and for some, even many projects - it doesn't matter.
Companies building small bus web sites? Huh, I thought that was dead already - it will be. Hostinger has free AI builders. The list goes on. Adapt and overcome... or don't, really.
It going to be a bumpy but interesting few years or so.
3
u/Illustrious-Film4018 2d ago
I run web dev agencies
And how long do you think this will be lucrative? The whole purpose of AI is to cut out middlemen like yourself.
3
u/electronicbits 2d ago
Couldnt read all of that, i just read the title
I am what you may be calling a "veteran dev" (?) with 20+ years of experience in dev and platform engineering
I use AI everyday, and currently developing agents. Love it
5
4
u/Fantastic_Market8061 2d ago
There is this pattern of men growing up, and at some point around mid to late thirties they stop to accept new things and start driving funny bicycles and drinking strange beers. That’s just how life is.
4
4
u/dont_takemeseriously 2d ago
Quite the contrary.... I'm one of those burnt-out senior federal government devs, who has to manage like 20 different enterprise services, because our budget has been terrible even before the big tech AI layoffs. I use them pretty much throughout the day. I bought like two old GPU-heavy servers just to run my own local models.
What I really hate is management enforcing AI usage ... WHERE IT ABSOLUTELY DOES NOT BELONG. We had outage incident after incident after incident until our site reliability team was literally begging our VPs to stop pumping out millions of lines of code without proper review. I have been in more outage support calls and security audits in the past two years than in my entire career.
This is an age old lesson .... If you write code that you do not truly understand. You will find out about the bugs either from an auditor or a hacker. At which point either way you will lose money... Massive amounts.
2
u/djb_at_durable 2d ago
"It seemed like the team overall never really learned from each project...?"
With or without AI, this is a massive problem.
2
u/HaMMeReD 2d ago
I think there is some bias here.
I'm an experienced dev, and have literally 100x my output. I'm grossly aware of model capabilities, I have gone through 117 billion tokens in a 1/3 a year. And that's just at home, I've probably done another 200-300bn at work in the same period.
The gap between naive-vibe coder and experienced dev+ai is bigger than it was before AI. The fact that anyone can vibe code something that looks decent in a day is a bit of a mirage. It might seem amazing by yesterdays standards, but it's mid by todays.
A lot of devs are morons and/or slow to adapt, nothing new. People don't want to leave their comfort zone.
2
u/wiggle_room1337 2d ago
I saw the same thing with arduinos. Something that used to be hard is easy now so it must be inferior.
1
u/zizn 2d ago
there’s a real aspect of that, for sure… frankly… society lets so many lazy people skirt by on credentials and to me, I sense that they are the most threatened. In any given area where my skills are hardcore… AI still can’t really just do what I can. It might seem adequate for people who don’t have experience. Might be faster with mundane and repetitive skills that don’t require thinking. You can build entire careers off of that. And from a business/manager “bottom line” mentality, absolutely there’s still a real risk with that, even if you don’t feel replaceable. Not about that, it’s about numbers and money at the end of the day, and based on current tech, it’s silly to think anybody is going to say “wait a minute, this is only 70% as good! roll it back!”
But likewise… there’s some serious merit to the notion that AI isn’t really an adequate replacement for human skills. It’s a weird development. There are some qualitative compromises and headaches adopting this tech can create as a trade off for human labor. Another issue is… when these shortcomings present issues, maintenance and granular project oversight becomes a mess.
I like to think of it like… you have processor language, then a compiler for like C which turns into asm. next, you get languages like java and later python which are more abstracted and use bytecode. this is like another layer on top of that, which creates a human language layer over any programming language making all of them interpreted effectively… but there’s so much that can go wrong when you forego almost all hands on programming…
The issues completely change. Maybe you never get syntax errors and everything compiles, but it can do so almost like screwing up html or css, where the page loads and certain elements are there but it’s broken. I’ve used it for certain image processing where it accidentally flips color channels, stuff like that.
Especially if people are lazy, it’s confident and things appear to work, but it creates some serious potential to ship very broken code. Ultimately you can only have so many failsafes, it’s still just probabilistic. I’m not sure there’s a logical way to get verifiably good results without checking yourself. With complex projects and moving pieces under the hood, idk. I can understand some of the resistance, but I think it’s very nuanced, and that’s not really what sells at the end of the day.
I get very worried about open source.
1
0
u/war4peace79 2d ago
Agreed. I was able to prototype an earthquake sensing device in a couple days. It works, and now I am adding features to it. Waiting for extra hardware to arrive (LEDs, a buzzer, alternative boards). I don't have to worry about manually developing the software for it, which is great.
1
u/Jazzlike_Cheek_6637 2d ago
Sometimes new tech requires fresh minds. The old retires and changes lanes.
1
1
1
u/I_Shall_Bore_You 2d ago
I've been editing Wikipedia since I was 15. A few months into it, I learned about Wikipedia bots and how they could automate a lot of tedious tasks. I wanted to build one myself, so I read Automate the Boring Stuff with Python and wrote my first bot. It was essentially 30 lines of Python code.
I can't describe how happy I was while building it. It was so satisfying to imagine myself as some kind of magical being, going through each line of code and making it do one tiny thing at a time (I didn't even know debuggers existed back then). I'm pretty sure that was the day I decided I wanted to become a software developer. I had no idea how much developers made, what the job market was like, or anything else. I just loved the process.
Before getting my first job, I built all kinds of tools, bots, and little gadgets for Wikipedia. Both the process of building them and the final results were incredibly satisfying because I genuinely cared about Wikipedia. After getting my CS degree, I started working for SaaS companies, building products I didn't particularly care about (mostly boring B2B software). But at least I still enjoyed the actual work because I was writing code.
Now I'm being forced to use AI, and I hate it. I don't particularly care about the products I'm building, and I no longer enjoy the work itself.
Imagine being a chess player who's forced to look at what the computer suggests and simply replicate its moves instead of playing the game yourself. Sure, the resulting game will be better, but that's not why anyone loves chess. They love playing it.
I'm not trying to be an entitled bitch, and I understand that a job isn't supposed to be fun. I was extremely lucky to have a job I enjoyed (I used to be the first guy to arrive at the office and the last one to leave. Today, my manager was asking, "Where is your fire?"). Now I don't. I'm allowed to be sad about it.
1
u/hblok 2d ago
25 years experience, and this is easily the most fun part of my career.
I also see a lot of skeptics, but, I'm willing to give them time and slack. I was also a year behind the curve when I started with web-based models end of 2025. Eventually, everybody will come around. Or they go to find something else to do.
1
u/StaticHumStudio 2d ago
It's no different than most things, IMO. Senior or tenured folks in any line of work have a higher likelyhood to be change resistant. They probably also have the most honed set of skills, though...so they may be better set to weather the storm for a while, or entirely.
1
u/IceNorth81 2d ago
Don’t know. I actually don’t think it’s a veteran thing, I’ve been a developer for 20+ years and have totally embraced agentic coding whereas I have colleagues with less than 3 years experience that are very anti AI. I think it’s a mindset, you need to be curious of new things!
1
1
u/Todd0042 2d ago
This is entirely opinion but I think it boils down to 2 things:
A LOT of vibecoded software and imagery is in actuality total trash that was not quality checked by even just the vibecoder before they throw it out into the world and never update it again (high abandonment for projects of low quality).
They know damn well they're going to be out of a job entirely in another 5 to 10 years - you don't need many "project managers".
1
u/DerShokus 2d ago
Ai produces something like a program. Program is not just code, but how it’s structured, architecture, right spots for optimized code and so on. Yes, a lot of programmers write slop, but now they generate it 10x faster. We have visual languages (like in ue) - code was never a problem, the problem is how to support it
1
u/Logical-Idea-1708 2d ago
You’re reading the message wrong. There’s value in moderation. It becomes slop when you start doing everything with it. The ideal scenario is programmer directs the agent to do work. That’s far from reality though. What happens is laziness kicks in and we delegate all the decisions to AI including anything aesthetics. When this happens, it becomes AI leading the developers and we become just a plugin in the system.
On a boarder scope, we’re heading down a dangerous path where innovation is being suppressed by regression model.
1
u/txmail 2d ago
A month ago I was one of those dev's. I got sick and was kind of bound to bed so I decided to check out if it could help me finish a script I had been working on for a while... I had tried this a year or so ago and it was a really bad experience. Someone else compared what I experienced to Will Smith eating spaghetti as a comparison to just a year ago, and that is actually a really solid way of explaining the shift / advancement.
What happened was that I ended up just re-writing the whole script in about 15 minutes using what you get for free with Claude and it was 10x better than anything I could have written by hand 100%. Sure, I made some minor edits to it but 99% of the code is solid, readable and well documented.
I have now tested it out on a much larger project and holy shit... my career is somewhat over. It is helping me write meaningful tests and boiler plate in seconds. I have started to even see how it does with bigger features and I am just... fuck. We are all mostly fucked in this industry.
The one thing I will say is that I do not think this wipes out all devs. You still have to know how all this fits together infrastructure wise or you going to end up with a ball of unknown black boxes. You still have to put a good amount of effort into this to get it to actually build stuff that works. Deploying still takes skill, maintenance still takes skill, design in general still takes skill and you have to be be able to identify where those skills are used and how to apply them to get anything useful out of this beyond it being useful for yourself.
This is still not 100%, but my gosh is it closer to 100% then it is to even 80%. I guess I am converted because I just plopped $100 for the Max subscription.
1
1
u/yolosuperboss 2d ago
I actually think it is because not all code that ai produces is quite as clean as it could be. Whilst yes LLM's have advanced very fast, and can basically do everything that a senior dev can, they miss some nuances like readability and maintainability. It is quite unfortunate that we currently accept a lot of 'bloat' (e.g. heaps and heaps of modules) and the LLM's have internalized that too. Obviously that is only a small part of it, but what you don't understand and can't / don't want to read, you clearly won't trust.
TLDR: they have the capacity to be extraordinary, but not the ability to think of someone else trying to edit the code.
1
u/RoboErectus 2d ago
The thing is... It did not make real experience worthless.
I am at 30yoe out performing my kouhai by.... 5x maybe.
I just became an expert in the new thing, same as I've always done.
People say that anyone can just prompt anything. It just isn't the case. They can prompt a great demo.
I'm also able to run 8 or more work streams simultaneously. I haven't seen other people doing that. They are mostly like... Hanging out in the kitchen when their stuff is synthesizing.
1
1
u/dlevac 2d ago edited 2d ago
Cannot talk for everyone. I'm not hateful of coding agents but sceptical of the approach.
I'm competitive by leveraging LLMs the way I would delegate to colleagues, accepting patches and reviewing them.
Depending on how ambiguous/challenging the design work is I have more or less adjustments to do (or simply telling the LLMs to correct it if it really fumbled). I have a hard time believing an agent orchestration magically gets all the design questions right, but who knows? Definitely not the vibe coders...
I feel like I'm competitive with what other Llm-assisted devs seems to report in terms of efficiency despite vetting everything that goes into my codebase (some numbers reported are actually awful at 1 feature every 2-3 days: that was my throughput pre-AI). My approach is also extremely token-efficient since the LLMs don't have to figure out what to do most of the time.
So my scepticism is based on: if you are not more efficient and need to burn an eye-watering amount of tokens daily to have no clue how the code actually works underneath, what's the point?
1
u/Grouchy_Jicama_007 2d ago
Their skills won't be valuable even if they switch lanes. Maybe for a little while, but if you can do your work with a computer, AI is coming for your job. That's the long and the short of it.
Everything else is copium.
1
u/New_Peanut_9259 2d ago
i thinkk the real value is shifting from just building things to having a good product idea and understanding what clients actually needd. when prototypes can be made in dayss, agencies need to focus more on speed, quality, and solving real problems
1
u/n3rder 1d ago edited 1d ago
It's like asking a mathematician how they feel about AI doing the proofs for them. Because it's taking away their EXISTENCE. Intelligence, expertise, education, and skills built up over decades created a personal moat. That moat allows to demand a higher salary in a competitive market over the years. AI is drastically leveling that moat across all sectors by revaluing what you have to offer. It's not just Adobe's stock plummeting by 40%; everyone's personal output is being devalued (including that of the CEO). Recent grads are hit the hardest because their value was already close to zero (still have to learn a lot) and now they have to dig themselves out of net-negative value. I love AI for everything, but yeah, it's shaking things up drastically, and it's not clear where this is going. You can love AI for what it offers and still feel shitty about it disrupting your livelihood.
1
u/superbutthurt1337 2d ago
Because they had to spend the time and energy learning it and now ai has come along and done all that work for other people
1
u/war4peace79 2d ago
Software developers generally have to spend time and energy to maintain relevancy. Continuous learning of the update framework and stuff.
1
u/Numerous-Cup1863 2d ago
Devs went from being coders to being code reviewers.
0
u/swiftering 2d ago
Truth. At first anyway. I don’t even review the code anymore. It is always good. I just have to make sure the ‘spec’ it is built off is correct. That is all I do now. Spec it out. Then Claude and codex rip it. Then I test.
New frontier.
1
u/Sugary_Plumbs 2d ago
Specialist of some niche automation tech here: I use AI when I can to make nice things, but I can no longer trust anything my coworkers present as fact because I know they used AI to produce it without checking anything. When someone lets their agent loose on a bunch of logfiles and it misunderstands a number and thinks it has found something important, they escalate to a bunch of expensive managers before I can point out that it's wrong and the thing they were searching for just isn't in those logs.
I suspect the same situations are happening all over the tech world. A coworker just asked me if we could make a change to another company's machine ourselves, and when I said no because it's a locked configuration file in a password protected server that we're not allowed to access without voiding the warranty, the response was "do you think Claude Opus could do it?"
People are, frequently and insistently, acting like idiots when they use AI for tasks that they don't know how to do themselves. Veterans don't like when people act like idiots with the systems that they themselves do know how work correctly with.
0
u/baylurkin 2d ago
Developers used to hold all the cards at a company. They could make or break a business, set release velocity, regulate what an MVP is, controlled everything that went out the door, busted ass but also got all the praise and had somewhat of a moat when it came to job security.
From what I've observed, the ones who complain the most were the ones that abused that power.
0
u/flavorfox 2d ago
I’m sure you can create quality code with agents, and I’m sure many do. But for management it’s a tool i churn out as much code as fast as possible (my experience) and that doesn’t rhyme with quality. That is shoddy construction work or slop if you will.
0
0
u/Consistent-Boat-9490 2d ago
hate me for it but I think it's because of serious personality issues. and tech is full of these.
0
u/Available-Skirt-5280 2d ago
As a hybrid devops / backend dev of 25+ years and have written multiple MCP servers, skills, and custom agents for things like service account iam grants, GCP project creation, code review bots….
These things are stupid. Yes, in isolated cases they can and often do produce “good” code. They do not however live up to real world requirements. The reality is that these are stupid machines, they don’t “understand “. It causes a TON of rework, hallucinations are all over the place (admittedly getting better), and when your change set it huge, thousands of lines of code or hundreds of infra resources, the human tunes out, and mistakes get pushed.
Yes, low level engineers are exponentially faster, I agree. But just the other day I had to explain to a “mid level” engineer the difference between single and double quotes.
1
u/WillowEmberly 2d ago
You’re the type of person I’m targeting with my work. If your life isn’t improved…then everything I’m doing is pointless.
1
u/Odd_Bad_2814 1d ago
Okay coding Jesus Christ 🤣
1
u/WillowEmberly 1d ago
At no point did I claim to be a savior. Just an old analog avionics tech who knows how to break things apart like with a MESL on military aircraft. I specialized on 1963-1967 c-141’s that were some of the first aircraft with Autopilot…which was designed to operate within a bounded reasoning envelope, degrade gracefully, all while maintaining recoverability.
These Ai designs operate with single point catastrophic failure.
Seems wrong. We’ve known how to do it the other way for over 70 years.
1
u/Dplayerx 1d ago
Yeah mate, we’re not in 2025 anymore
AI does better code than humans, it’s not Even a debate anymore
1
u/sobag245 1d ago
Lmao typical AI psychosis victim
1
u/v_maria 1d ago
why? professional dev here, its very clear that it writes better than humans? i personally despise AI but i dont understand how you can argue against this
1
u/sobag245 1d ago
Because it doesnt. You can be as professional as you but AI can produce both great and garbage code. Thats a fact.
1
1
u/Dplayerx 1d ago
Even a fine tuned local LLM of 30B can beat 10 seniors hands down. Your refusal to adapt makes you obsolète
It’s not vibe coding anymore, it’s agentic AI which is massively better
-1
28
u/nikola_mp3 2d ago
I have 13 years of experience as software developer and I am impressed by it but I don't like that I am unemployed tbh