I love that the AI boom is causing us to revisit some really important questions.
Uber : How should we be organized to make real progress?
Uber paired engineers with domain experts from 16 different business areas. The engineers shadowed these experts, learned how they worked, then worked together with these people to redefine entire workflows around agentic solutions.
They've seen impressive gains in just two months.
The biggest lesson: The best AI opportunities are rarely visible from the outside. You discover them by sitting next to the people doing the work, understanding every friction point, and building with them, not for them.
Uber's CTO on Agentic Pods at Uber LinkedIn.com, Jul 7 2026
"Uncle" Bob Martin : How do you know that the code is good?
Uncle Bob literally wrote the book on writing good code.* He now says that he isn't reading the code generated by AI agents. Instead, he is validating that code through tests and metrics.
I don't review code written by agents. I measure things like test coverage, dependency structure, cyclomatic complexity, module sizes, mutation testing, etc.
Much can be inferred about the quality of the code from those metrics. The code itself I leave to the AI.
Humans are slow at code. To get productivity we humans need to disengage from code and manage from a higher level.
unclebobmartin X.com, Apr 14 2026
I'm significantly older than you. I started coding in the late 60s. My current strategy is to not read any of the code written by my agents. That's the only way I can take advantage of their productivity. What I do instead is to surround the agents with extreme constraints. Unit tests, gherkin tests, QA procedures, quality metrics, mutation testing, test coverage, and a plethora of others. In the end, I have very high confidence in the code they produce because they've had to run the gauntlet of all of my constraints and tests.
unclebobmartin X.com, Jul 23 2026