4 ms·
If you expect to be able to prompt a chatbot and then not TEST that the code it wrote for you works, you're going to have a bad time. If you're willing to put
by simonw 2y ago
If you expect to be able to prompt a chatbot and then not TEST that the code it wrote for you works, you're going to have a bad time.
If you're willing to put in that QA work yourself the productivity boost you can get them from is immense.
And honestly, working with the best human programmer in the world won't guarantee that the software they produce is the exact software that you wanted. Details are always lost in the communication between the person who wants the software and the person who builds it
What matters most is the dialog and speed of iteration that you can achieve to converge on the right product.
- jebarker 2y agoI think the reason that I haven't felt the productivity boost is because my work is mostly debugging and fixing existing code in a complicated codebase. Rarely is it writing new greenfield code. LLMs have so far struggled to be useful in this setting as it's more like the QA part of the workflow you're suggesting.
- robertlagrant 2y ago> If you're willing to put in that QA work yourself the productivity boost you can get them from is immense. Isn't that work more than half the work of programming? I seem to find myself spending much more time on test code than on application code.
- YeGoblynQueenne 2y ago>> If you expect to be able to prompt a chatbot and then not TEST that the code it wrote for you works, you're going to have a bad time. Then what do you need the chatbot for? I have to do that with my own code all the time anyway. What's the benefit?