It is a part of gaining experience and knowledge though. If you aren't a senior right now, eventually you will be, and one of the expectations will be that you can read and review more novice programmers code and help them improve it, and lend a helping hand when you can. Eventually, all you do will be to review the work others have done after you instructing them to do the thing. Not to mention reading through really great written programs is personally a great joy for me, and almost always learn something new.
But, probably remaining a developer who runs through tickets in JIRA without much care for collaboration could be feasible in some type of companies too.
Then use better software engineering paradigms in how your AI builds projects.
I find the more I specify about all the stuff I thought was hilariously pedantic hyper-analysis when I was in school, the less I have to interpret.
If you use test-driven, well-encapsulated object oriented programming in an idiomatic form for your language/framework, all you really end up needing to review is "are these tests really testing everything they should."