I do. Part of my job involves writing code and I often don’t even know where to start. When I get the first draft I’ll know which documentation to read, and then I make it actually work. Even when the LLM fails completely, writing its prompt serves as a rubber duck.
So do you frame the problem to the LLM, get it to spit out an example piece of code and then run through that initial attempt to get an idea of how to approach the problem? Kind of like prototyping the problem?
I take it you find that more efficient than traditional code planning methods? Or do you then start building flow charts/pseudo code from that prototype and confirm the logic to build more readable or efficient code?
I do. Part of my job involves writing code and I often don’t even know where to start. When I get the first draft I’ll know which documentation to read, and then I make it actually work. Even when the LLM fails completely, writing its prompt serves as a rubber duck.
So do you frame the problem to the LLM, get it to spit out an example piece of code and then run through that initial attempt to get an idea of how to approach the problem? Kind of like prototyping the problem?
I take it you find that more efficient than traditional code planning methods? Or do you then start building flow charts/pseudo code from that prototype and confirm the logic to build more readable or efficient code?
Yes. Maybe? I don’t know traditional code planning methods. I guess?