Hacker News new | past | comments | ask | show | jobs | submit
what I generally found is that with LLM generated code the best way is to embrace the unix philosophy, create tools that perform singular objectives.

I wound up with a bunch of LLM written tools that I don't even bother to try and understand much less review, they either function as desired or I set an LLM to make them function (or just rewrite them) and then forget about them. make sure to keep a prompt in each tool's directory and update it an needed.

sadly this isn't always possible, some systems require complexity at some level. in those cases the tools from above become functions and objects and more care needs to be taken into orchestrating them to limit the necessity of review. data oriented design approaches and functional programming help here.

This is the winning strategy, and not just in software development.
omg, this will be harvard's breakthrough next year