This should give a second life to Test-Driven Development.
One of the under-appreciated wisdoms of TDD is that there is a complexity asymmetry in many problems between finding a solution and (fully or partially) verifying it. Examples of asymmetric problems: inverting matrices, sorting an array, computing a function's gradient, compressing a byte stream, etc.
Human writes the easier part -- the test suite, the language model writes the harder part -- the solution. This can be a net gain in productivity.
One of the under-appreciated wisdoms of TDD is that there is a complexity asymmetry in many problems between finding a solution and (fully or partially) verifying it. Examples of asymmetric problems: inverting matrices, sorting an array, computing a function's gradient, compressing a byte stream, etc.
Human writes the easier part -- the test suite, the language model writes the harder part -- the solution. This can be a net gain in productivity.