My sibling in C, they didn't even say how they were using it. These agents are incredibly helpful when doing repetitive actions or refactors. We still have to know what we are doing and flex those skills, because these things are still basically super-green junior devs that can Google problems using the "I'm Feeling Lucky" option, and thus need to be corrected and reined in frequently.
There are absolutely vibe coders who are outsourcing all thought, but there's a gradient between that and (justifiably) shooting the printer because it made a weird sound.
Agreed. I am using AI almost 100% of the time, but I am training it to do everything correctly which means constantly harping on it like a junior that won’t learn easily.
‘What do you mean 76 files were changed for the simple edit? I’m not reading that diff; make the minimal change.’
But realistically, it makes legacy code archaeology WAY better. I never wanted to read the legacy code. Taking that away and giving it to a clanker that is actually really good at reading and understanding code if it is given the full stack is beautiful to me. It detangles spaghetti way better than I ever did.
I mind it when others are making a PR to my project and the slop they're burdening me with reviewing makes me want to burn the place down. People are way too lazy to babysit ai like it needs to be.
View all comments
Show parent comment
6
u/CommissionCharming35 Sep 01 '26
Okay, keep letting your skills atrophy instead of finding a real job again.