| I experimented with coding with GPT a few times now. GPT is legitimately interesting as an alternative search interface to StackOverflow. I've found that 15 to 45 minutes of searching with Google/StackOverflow can be reduced to just 5 minutes with GPT. But beyond that, it's been very disappointing. Whenever I've tried getting it to write something even slightly non-trivial (i.e. tougher than just copy/pasting from online documentation or an answer on StackOverflow) it's produced code that is horribly broken, but where the flaws are subtle enough that they might not pop out right away to a novice programmer. It has consistently struggled with programming problems that I would rate at 4/10 or 5/10 difficulty. Most of the code I write is fairly trivial, but it's glue code that is highly specific to my particular code base, so GPT isn't helpful because it doesn't know about my codebase, and if you try to copy/paste your large chunks of your codebase into the prompt it runs into issues with forgetting. And GPT isn't helpful for the non-trivial parts of my code either (as mentioned above). So what's left? So when I see people say that it 10x'ed their productivity, I wonder if they exclusively write very trivial code that is effectively copy/paste from Stack Overflow or if they've allowed GPT to fill their codebases with flawed code without realizing it. Maybe future iterations of GPT will get it. GPT4 is definitely not there yet. |
I usually prompt it with short questions, but I recently saw a video where the person provided a lengthy (50 - 150 words) prompts detailing the requirements for what they were requesting. I was shocked at the results. (Still required iterations of corrections/modifications though)
I haven’t tried it myself yet, but it’s an avenue that might yield better results than what you’ve experienced — perhaps even vastly better results.