|
|
|
|
|
by Wool2662
557 days ago
|
|
I like to do a few things:
- Bounce ideas off it. How would you stucture this and why?
- Simplify code i have written in a first draft
- review my changes
- ask about why something doesn't work (if the first answer doesn't help the next one won't either in my experience)
- document this code
- write tests for this (very useful, oftentimes gives you great initial tests and an easy test boiler plate to extend with your edge cases) I use it a lot like a pair programmer, just to get out of my tunnel vision. I wrote the code, it can be hard for me to see the flaws since i looked at it all day already. It helps to get a different perspective. The thing I feel is important is that you are ready to throw away anything it generates the second it doesn't feel immediately useful. I don't retry/reword request. I think I use something from about 60% of requests and the rest os discarded fully. |
|