You say “this shit” while not understanding what they are doing. As per their listed guidelines, they use it for documentation, generating boilerplate and other kinds of repetitive tasks. Newsflash, that’s how it is used in most companies I know, since chatGPT’s inception. This is not vibe coding, this is using the tool as intended.
You do use autocomplete and autocorrect in your phone, right?
You say “this shit” while not understanding what they are doing.
Oh, I understand fine.
I’m a software developer, and the company I currently work for has mandated that we make ai coding tools (aka “this shit”) part of our daily workflows. I’ve been using this shit every day for the last year and a half. I’m not a “vibe coder”, either. I have 15 years of experience in this industry, and this shit has universally made my job worse. Even for simple or repetitive tasks it requires constant babysitting, and when it does actually produce functional code, it’s always messy, verbose, and fails to match the style guidelines of our app, meaning I have to waste even more time cleaning THIS SHIT up (or prompting it through that cleanup process — which wastes my time AND my patience).
And most people I work with are a lot lazier with it than I am, which means now I have to spend twice as much time on code reviews to make sure that no one is pushing MORE OF THIS BROKEN FUCKING SHIT into our codebase. There have already been several major production outages at the company because of AI generated code committed by other teams, and in general the quality of our apps has fallen a lot.
Maybe AI tools are fine in isolation, I don’t know. I’ve never asked one to build shitty node.js app #1743168… But if you set THIS SHIT lose on a mature codebase, that codebase immediately gets worse. It introduces bugs, makes the code harder to read, makes the code harder to maintain, and worst of all, it decreases the code literacy of all the developers using it.
When you write your own code, there’s a self-reinforcement mechanism at play, the same as how taking notes in class helps you retain the information better than just passively listening. You don’t get that when you just auto-generate and then passively review code, so we’re starting to see a real “brain drain” where AI tools are harming developers’ understanding of the apps they work on. This isn’t hypothetical, I’ve seen this first hand. A year ago I could ask fellow developers to explain to me in detail the code they wrote three or four weeks ago and they could do it just fine. Now, devs can barely explain code from last week — which, as I’m sure you can imagine, greatly slows down the inevitable debugging that follows when the code they don’t fully understand inevitably breaks.
So yeah, I understand perfectly well what’s going on with this stupid, wasteful, tech-debt producing SHIT, and even though I can’t avoid it in the software I write, I’m sure as shit going to avoid it in the software I use.
Yep, I’ve noticed the people who have to use AI the most are usually the most noob people on the team. Reviewing the mountain of slop code they post is aggravating. Honestly, I don’t even review it anymore. Fuck it. If you’re not gonna take the time to write something good, I’m not gonna take the time to give you an honest review.
Hopefully people who care will start (and for those that already are, continue) to contribute to open software projects that don’t include this shit.
You say “this shit” while not understanding what they are doing. As per their listed guidelines, they use it for documentation, generating boilerplate and other kinds of repetitive tasks. Newsflash, that’s how it is used in most companies I know, since chatGPT’s inception. This is not vibe coding, this is using the tool as intended.
You do use autocomplete and autocorrect in your phone, right?
Oh, I understand fine.
I’m a software developer, and the company I currently work for has mandated that we make ai coding tools (aka “this shit”) part of our daily workflows. I’ve been using this shit every day for the last year and a half. I’m not a “vibe coder”, either. I have 15 years of experience in this industry, and this shit has universally made my job worse. Even for simple or repetitive tasks it requires constant babysitting, and when it does actually produce functional code, it’s always messy, verbose, and fails to match the style guidelines of our app, meaning I have to waste even more time cleaning THIS SHIT up (or prompting it through that cleanup process — which wastes my time AND my patience).
And most people I work with are a lot lazier with it than I am, which means now I have to spend twice as much time on code reviews to make sure that no one is pushing MORE OF THIS BROKEN FUCKING SHIT into our codebase. There have already been several major production outages at the company because of AI generated code committed by other teams, and in general the quality of our apps has fallen a lot.
Maybe AI tools are fine in isolation, I don’t know. I’ve never asked one to build shitty node.js app #1743168… But if you set THIS SHIT lose on a mature codebase, that codebase immediately gets worse. It introduces bugs, makes the code harder to read, makes the code harder to maintain, and worst of all, it decreases the code literacy of all the developers using it.
When you write your own code, there’s a self-reinforcement mechanism at play, the same as how taking notes in class helps you retain the information better than just passively listening. You don’t get that when you just auto-generate and then passively review code, so we’re starting to see a real “brain drain” where AI tools are harming developers’ understanding of the apps they work on. This isn’t hypothetical, I’ve seen this first hand. A year ago I could ask fellow developers to explain to me in detail the code they wrote three or four weeks ago and they could do it just fine. Now, devs can barely explain code from last week — which, as I’m sure you can imagine, greatly slows down the inevitable debugging that follows when the code they don’t fully understand inevitably breaks.
So yeah, I understand perfectly well what’s going on with this stupid, wasteful, tech-debt producing SHIT, and even though I can’t avoid it in the software I write, I’m sure as shit going to avoid it in the software I use.
Shit.
Yep, I’ve noticed the people who have to use AI the most are usually the most noob people on the team. Reviewing the mountain of slop code they post is aggravating. Honestly, I don’t even review it anymore. Fuck it. If you’re not gonna take the time to write something good, I’m not gonna take the time to give you an honest review.
They’ll reap what they sow. More bugs, more shit.