Why are developers so attached to computer gibberish
Why are developers so attached to computer gibberish
You're viewing a single thread.
18 comments
-
I've been coding for like.. 25 years, mostly professionally.
I've been learning game development on and off for years and just started with Godot and c#. I use deepseek and chatgpt sometimes because I know what I want to do just not the best syntax to do it (and throw in having to avoid dynamic stuff for iOS' AoT compiler)
Both frequently forget the language, library, task or context. Context is ok, but asking for how to do X in Y and it gives you an answer predicated on using Z (which l, due to unfamiliarity you don't find out until after starting to implement it) sucks.
I get a slightly easier day when it works. But I've lost days of time to it fucking with me. Eventually you become so wary that it really is just a glorified search engine now. I tell it show me X and only the code, that seems to be the fastest way to get what I need and confirm it's not hallucinating a different environment or whatever.
People with less experience in general will suffer far worse because those pitfalls won't be obvious to them.
GPT got worse with the most recent update, answers ignore large chunks of the prompt and as they distill further I think that will get worse.
Tl;Dr AI isn't very good at programming and seems to have gotten worse (at least with specific questions Vs general ones)
-
People with less experience
I now refer to an Amazon review on a scripting language:
-
How would a programming book have that kind of mistakes? Do they manually type the code, and output separately?
Any semi-competent programmer will copy paste the code to the terminal and copy the output.
And any competent programmer will make sure the output is auto generated from the code so there's no mistakes.
-
People write books. People are imperfect. People write imperfect books. It's not hard to copy / pasta the wrong notes when assembling the bones of a book.
-
-
-
18 comments