Comment on Developer survey shows trust in AI coding tools is falling as usage rises
Feyd@programming.dev 8 months ago
There’s relatively little debate among developers that the tools are or ought to be useful,
Yes there is. No one wants to listen to us. I’ve had 3 levels of people above me ask me how I’ve incorporated AI into my workflow. I don’t get any pushback because my effectiveness is well known, yet the top down edict that everyone else use these shitty tools continues unabated.
Where I work, my skip-levels have started debating on whether they want to consider if an engineer uses AI as a factor for reviews, pay raises and incentives, and are tracking who uses it by way of licenses.
It's a bit ridiculous IMO because they're essentially saying "we don't care if slop makes it into the code base, so long as you are using AI, you will remain gainfully employed."
I’ve seen a lot of stupid shit over my career but this AI zealotry just takes the cake.
Everyone is so convinced these tools will make software get made faster, but I’m not even convinced that it gives even a modest benefit. For me personally they definitely don’t, and it seems to lead junior devs horribly astray as often as it helps speed them up.
It feels like I’m not even looking at the same reality as everyone else at this point.
I wish I had one like you at where I work, just to keep sane for a bit longer. Everyone else is just way too into this shit even though for most it seems like a gigantic time sink.
I mean “ought to be useful,” sure that would be nice. They ain’t, but perhaps “ought to be.”
Serinus@lemmy.world 8 months ago
It’s useful for things I’d otherwise Google. It makes a great ORM, when you know exactly what you want to do with a lot of mundane code. And it’s so much better than adding a framework for an ORM.
Feyd@programming.dev 8 months ago
I don’t like ORMs, but I’d rather use a battle tested ORM than some vibe coded data layer.
Serinus@lemmy.world 8 months ago
You know, you can just look at it. It’s pretty simple, easy to look at, pretty repetitive code where it’s generally pretty easy to spot if something’s wrong.
Vibe coding is more hitting “accept all” and not looking at it at all (or not knowing how to look at it).
Feyd@programming.dev 8 months ago
Or, I could just write it myself, instead of ending up like these guys sketch.dev/…/our-first-outage-from-llm-written-co…