Comment by pmarreck

I've noticed a few things that will cause it to write better code.

1) Asking it to write one feature at a time with test coverage, instead of the whole app at once.

2) You have to actually review and understand its changes in detail and be ready to often reject or ask for modifications. (Every time I've sleepily accepted Codeium Windsurf's recommendations without much interference has resulted in bad news.)

3) If the context gets too long it will start to "lose the plot" and make some repeated errors; that's the time to tell it to sum up what has been achieved thus far and to copy-paste that into a new context