Btw, the insight that reviewing code will become more important than producing code was introduced to me via this paper:

“Taking Flight with Copilot: Early insights and opportunities of AI-powered pair-programming tools”

https://dl.acm.org/doi/10.1145/3582083

My assertion that grappling with the increasing importance of code review is literally a business imperative came to me while reading @grimalkina @KFosterMarks and @CSLee’s excellent work on AI skill threat:

https://www.pluralsight.com/resource-center/guides/new-developer-research-paper

So, why are so many executives and investors overlooking this very basic reality that code produced is code which must be maintained, and that an acceleration of code produced thanks to gen AI means ~more risk~, not just more $$$?

I have friends who are Principal Engineers asking themselves this very question right now.

And in response, I point us to the classic Upton Sinclair quote:
“It is difficult to get a man to understand something, when his salary depends on his not understanding it.”

@anthrocypher I've got this in an upcoming publication:

"Every line of code written today represents a testing, complexity, maintenance and refactoring burden your team will bear tomorrow, and the reality is that none of our customers want code. Our customers want _utility and functionality;_ code is a liability we accept so we can deliver that functionality. GenAI or not, nobody wants or needs an arbitrary quantity of code for its own sake."