Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The solution to this if you want less specification in advance is to simply ask Codex a series of leading questions about a feature of fix. I typically start with something like “it seems like X could be improved with the addition of Y? Can you review the relevant parts of the codebase in a, b, and c to assess?” It will then do so and come back with a set of suggestions that follow this guidance, which you can revise and selectively tell it to implement. In my experience, this fills the context with the appropriate details to then let it make more of its own decisions in a generally correct way without as much handholding.


No it won't, it'll spend ten minutes and come back with "OK I've implemented a solution". I really wish it had a plan mode.


Mileage may vary, but I do the above all day long without issue.


Very odd, it's always really eager to implement things for me, I have to say "absolutely do NOT write any code before discussing" every time.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: