man does this dude think the hardest part about writing a book is fucking typing it out? someone give this dork a swirly
this post was submitted on 30 Jan 2026
138 points (92.6% liked)
Programming Circlejerk
278 readers
68 users here now
Community to talk about enlightened programming takes
Rules:
- read and follow the programming.dev code of conduct
- no flamewars
- mark your unjerks
- only programming related content allowed
- link to the original source
- do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.
founded 1 year ago
MODERATORS
guy in the business of vibe coding hypes up vibe coding
Pokémon Red & Blue was 373 KB. So much efficiency and creative coding made early high-content video games possible. Imagine how bloated that would be if it was vibe coded by AI
But could you imagine all the exploits we would have found by now? That special little coast line would have been nothing. Missing Number? Bet we would have had the whole Missing Alphabet haha.
3 months later they rehired all of those four engineers to fix all that bullshit useless code.
Techbros calculate programming skills by lines of code per shift.
It only makes sense that they would think "10x engineer" just means "types 10 times as fast."
Yea…..but how may developers are you going to have to pay to maintain that shit?
Fun story!
The CEO was charmed by some AI vibe dude who
- Absolutely ripped into multiple software departments about our "shit code"
- Bragged that he could do it faster and better with AI
CEO gave him a three month trial run to show it.
AI vibe dude spent the first two weeks showing off all this cool new frontend to managers. Nothing actually worked. They gave him a round of feedback.
Then he spent another two weeks struggling to meet the feedback.
They ended the trial because the AI Vibe coder dude couldn't handle system changes, how to fix bugs, implementing new feature requests without breaking old stuff, and didn't have any real coding skills. He barely lasted a month.
The first half of this story made me wonder if we were colleagues.
The second half was different though. Our guy was a personal friend of some high up, slandered the existing codebase without so much as even speaking to the existing devteam, and then took the better part of a year claiming he could replace the entire decade old codebase while making vague promises that it was coming soon. Meanwhile upper management was taking the slander seriously, punished my department and got a new manager for it. It wasnt until the new manager outed him as a fraud for his ass to finally get caught.
I doubt he was able to read the legacy codebase at all.
"Talent utilization crisis"
"Hire 1 engineer instead of 4"
Yes
There's going to be so much awful slop code everywhere in the future.
This is the real reason why all those scrappy rebels in sci-fi shows can hack into everything.
This was definitely written with AI.
I hate LinkedIn and all the fuck holes on it so god damn bad
Ah yes one of those bootlicking linkedin lunatics
"We're not in X, we're in Y"
squints suspiciously
Hahahaha this idiot thinks that it's the speed of our typing that ships code faster. He's in a knowledge shortage.
I’ve found that the people who understand these “agents” the least are the ones who are promoting them the most.
And everyone promotes them for tasks they aren't experts in.
Managers think they could replace devs, but never a manager.
Devs think they could replace management but never a senior developer.
Storyboard drawers think they can write screenplays. Screenplay writers think they can draw storyboards. Etc.
As an expert, you know how shit AI is in your own field, but surely those other jobs are simple enough to be replaced.
Let's be honest, though: they absolutely could replace management.
some management, sure. just like some of your coworkers could probably be replaced by AI. but not the competent ones, and not the essential ones.
and personally, I'd still rather work with an incompetent person who can improve than four incompetent chatbots
although I'd rather work with no incompetence at all
The principal task of a competent manager is, primarily, intervening between incompetent upper managers and actual workers. Replacing the incompetent manager removes the need for the competent one.
A good manager is both a coordinator and a filter. They deal with bs rolling down from above and keep their team running efficiently.
A good manager is worth their weight in gold. A bad manager isn't worth their weight in bullshit.
I've also enjoyed the term "shit umbrella" for a good manager.
load more comments
(1 replies)
It's very easy to replace something that was never critical to the process in the first place. My manager essentially updates my git tickets with what I did. We talk for 5 minutes a week. He just kinda lets me do my thing, I am fully aware of how lucky I am.
90% of my experience with management is having none at all would be a net benefit
why would we want to add ai to that mix
load more comments
(3 replies)
load more comments
(3 replies)
Stop hiring 20 managers. Hire 1 manager and have them in meetings all day so real work can be done.
Ah yes, the Fred Trump gambit.
My sister-in-law is a software engineer and project manager. This isn't groundbreaking news or anything but she said that her engineers are using generative AI like this. The problem is that it created exceedingly inefficient and bloated code that barely works. En masse it will bog down systems due to the exponential inefficiencies.
It's fine. Everything is fine.
So......why is she letting them, and not instead, like, not letting them?
I'm not her or her employer. It is an odd time for the coding industry. It'd be like a fish swimming against the manager/leader-lead river.
Yup, it's a junior dev that never learns, makes thousands of tiny mistakes that tolerance stack into a brittle gnarled mess.
load more comments
(3 replies)
"The new skill isn't typing faster".
Since I added a second keyboard I am programming twice as fast and don't even need AI!
One of our devs came to me with an LLM rewrite of some parts of our automation. Even at first glance you could see a lot was missed, the refactor simply wasn't going to work in that state and critical migration logic just wasn't present.
I binned the branch and did the refactor myself, as it would have taken more time to figure out the damage caused than just starting over.
So glad we now pay premium prices for RAM and non-volatile storage, just so some LLM can vomit up a reheated turd.
and that's the fucking crux of it right there, the damage. Any code base without someone smart enough to throw this trash out is going to take forever to fix or might just be too far gone to save
Last week, curious what would be generated, told Cursor (with Claude Opus 4.5) to create an animated LED strip effect for an ESP32 device in C. Pretty simple stuff. It thinks for a long time. Creates a ton of scaffolding, docs, step-by-step agentic checklists, even a Makefile to build and deploy the binary. It then says: "Done."
I go compile it. Lots of errors. I paste over the logs and ask it what's wrong. Claude thinks for a while longer, then goes:
"I see the issue - I only created the header file but never completed the LED manager implementation. Let me check what's there and finish the implementation."
Could you try something else and when it says it's done, ask it to check for errors first?
It said it had. Obviously, a fabrication. Even after it said it implemented it, it took a couple more hours of coaxing it and pointing whst should be done before it actually worked.
Point is, one shouldn't go near these LLMs for coding unless they know what to do and how to look for problems.
There isn't a talent shortage, there's a shortage of people who will take your shit at sub-par wages working two + jobs at your company.
Does he know what a technical debt is?
The most important thing in vibe coding is to cash the check and nope out of there before management realize what you've done.
The 1st major project in my first coding job made me understand technical debt even though I didn't know the name of it.
I suppose there are some people that just see spaghetti code and their only thought is to add more spaghetti code. Thankfully I also understood spaghetti code with my project in uni.
load more comments
(6 replies)
load more comments
(3 replies)
Prompt: "write a python script to create a thousand linkedin accounts with plausible sounding names, and then setup a cronjob to post every day a punchy linkedin just-so story explaining why everyone should be paying for my LLM and to keep paying for it when I jack up the price 100x to cover my expenses"
load more comments
(1 replies)
view more: next ›