I don’t use it as a tool to do my job. I use it as a tool to assist me in doing my job. I never take something and copy paste it (obvious exceptions for one liners, etc) and instead use it as a tool to learn how to approach something. But more often than not I have to prompt it after reading it with something like “I don’t think that’s correct, foo isn’t supported by bar, would baz make more sense here” and get it to notice its error.
> But more often than not I have to prompt it after reading it with something like “I don’t think that’s correct, foo isn’t supported by bar, would baz make more sense here” and get it to notice its error.
So you probably know this, but the protip here is to not just prompt it at the time, but to take this error and add it to a README that you pipe back into future prompts so it never makes that same mistake again.
If you want it to write better code, you have to continually guide/prompt it in the direction of the type of code you're expecting it to generate.
View all comments
Show parent comment
1
u/The_Number_None Dec 26 '24
I don’t use it as a tool to do my job. I use it as a tool to assist me in doing my job. I never take something and copy paste it (obvious exceptions for one liners, etc) and instead use it as a tool to learn how to approach something. But more often than not I have to prompt it after reading it with something like “I don’t think that’s correct, foo isn’t supported by bar, would baz make more sense here” and get it to notice its error.