463
If AI is so good at coding … where are the open source contributions?
(pivot-to-ai.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 May 2025
463 points (100.0% liked)
TechTakes
2215 readers
105 users here now
Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.
This is not debate club. Unless it’s amusing debate.
For actually-good tech, you want our NotAwfulTech community
founded 2 years ago
MODERATORS
Today the CISO of the company I work for suggested that we should get qodo.ai because it would "... help the developers improve code quality."
I wish I was making this up.
My boss is obsessed with Claude and ChatGPT, and loves to micromanage. Typically, if there's an issue with what a client is requesting, I'll approach him with:
He will then, almost always, ask if I've checked with the AI. I'll say no. He'll then send me chunks of unusable code that the AI has spat out, which almost always perfectly illuminate the first point I just explained to him.
It's getting very boring dealing with the roboloving freaks.
90% of developers are so bad, that even ChatGPT 3.5 is much better.
wow 90%, do you have actual studies to back up that number you're about to claim you didn't just pull out of your ass?
This reminds me of another post I'd read, "Hey, wait – is employee performance really Gaussian distributed??".
There's this phenomenon when you're an interviewer at a decently-funded start-up where you take a ton of interviews and say "OMG developers are so bad". But you've mistakenly defined "developer" as "person who applies for a developer job". GPT3.5 is certainly better at solving interview questions than 90% of the people who apply. But it's worse than the people who actually pass the interview. (In part because the interview is more than just implementing a standard interview problem.)
your post has done a significantly better job of understanding the issue than a rather-uncomfortably-large amount of programming.dev posters we get, and that's refreshing!
and, yep
I moderately regret this post
because the counterposter in question went on to have some decidedly "fucking ugggggggh" posts
ah well. so we learn.