Earlier quoted context omitted.
My "actual job" isn't to write code, but to solve problems. Writing code has just typically been how I've needed to solve those problems. That has increasingly shifted to "just" reviewing code and focusing on the architecture and domain models. I get to spend more time on my actual job.
> My "actual job" isn't to write code, but to solve problems. Yes, and there's often a benefit to having a human have an understanding of the concrete details of the system when you're trying to solve problems. > That has increasingly shifted to "just" reviewing code It takes longer to read code than to write code if you're trying to get the same level of understanding. You're gaining time by building up an understan…
It's important that when you solve problems by writing code, you go through all the use cases of your solution. In my experience, just reading the code given by someone else (either a human or machine) is not enough and you end up evaluating perhaps the main use cases and the style. Most of the times you will find gaps while writing the code yourself.