Comment by stpedgwdgfhgdd
1 year ago
Software development to me has always been about the 80-20 rule. You build 80% of the functionality in 20% of the time. Next you spent 80% of your time to build the remaining 20%.
With LLMs it feels we are getting near to 90-10. Finding the bug in those good-looking pieces of generated code is pretty hard. (After all, you did not pay a lot of attention to the generated code, it looked pretty solid) Some will argue that the LLM should spot the bug, Indeed, it should ask clarifications about the requirements. One day… but you need an expert to understand and answer the questions for that last 10%.
I feel like finding bugs in golang is a non issue. The language is typed, so obvious problems are caught early in the editor. Unit tests mop up the rest (unit tests which are also written by copilot in my case).
How I write unit tests: Open the chat menu, paste in function signature, describe the tests I want. Out pop the tests. Run, fix code as needed. Add more tests, etc. Super easy.
Or way easier, build an harness, then just copy-paste the few tests you created at the beginning, because test codes is the most repetitive code I've seen. No need to rely on external services and much more simpler to maintain and reason about.