Comment by netsharc
2 days ago
And sometimes this intern which can produce code at blazing speeds get some subtleties wrong, so you can never trust their output and have to check every time.
And when you point out the error they sometimes insist what they did is correct, or they confidently "correct" it to something still wrong.
> And sometimes this intern which can produce code at blazing speeds get some subtleties wrong, so you can never trust their output and have to check every time.
You're just describing junior employees lol.
Juniors turn to seniors. You can never trust AI won't glitch...
lol
> Juniors turn to seniors.
AI has gone from "codes like a student" to "fresh hire junior" to "nearly ready for next step in career" at about the same, tiny bit faster, calendar pace as humans.
> You can never trust AI won't glitch...
True.
https://en.wikipedia.org/wiki/Nobel_disease
https://en.wikipedia.org/wiki/Covfefe
https://en.wikipedia.org/wiki/Groupthink
https://en.wikipedia.org/wiki/Boris_Johnson
And?
4 replies →
Yes, I agree, AI's risk creating a huge pipeline problem.
thats the reason why I always focus on one function per thread / or one class per thread, and I copy it by hand in VS.NET, to exactly prevent this - never ever I would let it run "unattended" on the codebase :)
Babylon 5 Crusade had a device called The Apocalypse Box. It knew everything and you could ask it questions. Unfortunately, it lied strategically so as to both give you an edge here and there whilst it drove you insane with all the lying. I have always seen the similarity to large language models here myself and that was in 1999.
https://babylon5.fandom.com/wiki/Apocalypse_Box
What has surprised me is that JMS has never seemingly noticed this.