On average this triplicates the amount of time required for a major change, but significantly improves business logic correctness and code quality
epolanski on Hacker News
triplicates the amount of time required for a major change
In the thread “FrontierCode: An eval to measure whether you would actually merge the code”
Helped: Planning together, finding edge cases, and reviewing step by step.
Got in the way: Models delivering quality output autonomously and reviewing large changesets.
… Then I want to review step by step all the edits the model does. On average this triplicates the amount of time required for a major change, but significantly improves business logic correctness and code quality, with the major benefit that it will require significantly less maintenance down the line and thus ends up being both a benefit on one side, and to improve harness on the other (more quality code, proper information, better examples for the models in the future). The issue is: models are increasingly getting worse at this kind of work. …