You find yourself signing off on an overwhelming amount of raw code just to keep up with the output that’s expected these days.
Then you’re doing it wrong, very very wrong. And any management that expects you to “just read faster” is management you should be distancing yourself from at maximum possible speed.
No, you can’t review the volume of code that LLMs output, one engineer driving an LLM code generator can create code faster than 10 engineers can review it. However, one engineer driving an LLM code generator, then driving the same and other LLMs to review that code for correctness can.
You can, and also should, be developing documented requirements for EVERYTHING the code is doing - LLMs help accelerate that process too.
You can, and also should, be developing unit and integration tests which ensure that your implementation doesn’t regress as new features are added. LLMs help accelerate that process too.
You can, and also should, be using LLMs to review the requirements, implementation and tests to ensure they are all synchronized, aligned, saying what they do and doing what they say. LLMs help accelerate that process too.
You can, and also should, be doing all of the above for software developed without LLMs, but in my experience the vast majority of teams don’t do good implementation of all the pieces. LLMs are an opportunity to start.
Then you’re doing it wrong, very very wrong. And any management that expects you to “just read faster” is management you should be distancing yourself from at maximum possible speed.
No, you can’t review the volume of code that LLMs output, one engineer driving an LLM code generator can create code faster than 10 engineers can review it. However, one engineer driving an LLM code generator, then driving the same and other LLMs to review that code for correctness can.
You can, and also should, be developing documented requirements for EVERYTHING the code is doing - LLMs help accelerate that process too.
You can, and also should, be developing unit and integration tests which ensure that your implementation doesn’t regress as new features are added. LLMs help accelerate that process too.
You can, and also should, be using LLMs to review the requirements, implementation and tests to ensure they are all synchronized, aligned, saying what they do and doing what they say. LLMs help accelerate that process too.
You can, and also should, be doing all of the above for software developed without LLMs, but in my experience the vast majority of teams don’t do good implementation of all the pieces. LLMs are an opportunity to start.