Work on your workflow, not in it

Michael Gerber wrote in his book "The E-Myth Revisited":

Work on your business, not in your business.

The basic idea is that you should build your business as a system, and then get other people to run that system for you. He said you should build your business as a "franchise prototype": You should build it in such a way that can be replicated many thousands of times, regardless of whether you actually do so or not.

This is how I view myself going forward (in an increasingly AI-driven world) as a software engineer: My job as a software engineer is to work on the AI system that produces the software, not directly on the software itself. Failures at the AI implementation level should be fixed at the system level. When reviewing a PR I am not reviewing the code itself; I am reviewing the system that created the code and trying to move any improvements/fixes there.