AI Coding Made Code Review the Bottleneck. Now What? - Scrum.org Blog (Yuval Yeret · Yuval Yeret) https://www.scrum.org/resources/blog/ai-coding-made-code-review-bottleneck-now-what
AI Coding Made Code Review the Bottleneck. Now What? - Scrum.org Blog (Yuval Yeret · Yuval Yeret) https://www.scrum.org/resources/blog/ai-coding-made-code-review-bottleneck-now-what
It seems to me that
#Ukraine has figured out how to lay a siege from the inside out.
Typically a siege prevents goods from entering the target.
Ukranian kinetic sanctions prevent goods from leaving Russia. They are rewriting everything we knew about war and I suspect there are implications for #infosec regarding institutional awareness of defense-in-depth, dependency management, etc.
I notice indicators that Ukraine's military is using iterative development cycles and continuous improvement similar to #DevOps , #TheoryOfConstraints and Lean Production.
I wonder if there's discussion of this in Ukranian/Russian language forums because I don't see much in English (or Spanish).
Blogged: How to get the most from the constraint on your (testing) process - A review of The Phoenix Project by Gene Kim, Kevin Behr, and George Spafford

This book is a novel about the transformation of a company from one that experiences pain when it releases software into one that releases and maintains software easily. We can learn much from the …
"If they need to chase five different people for incomplete documents, you're not going to speed up said process by adding more lawyers to the department."
#ai #theoryofconstraints #lean #productivity
https://frederickvanbrabant.com/blog/2026-05-15-i-dont-think-ai-will-make-your-processes-go-faster/
"When we deploy a digital tool like email to speed up communication, or generative AI to create (sloppy) slide presentations quickly, we don’t automatically become better at our jobs. If these steps don’t improve the bottleneck in our process – the key link where the real value is produced – then, as in the chicken coop example, they’re just as likely to create pile-ups and distraction, without actually boosting our true productivity."
Excellent analysis in the article linked here -
"If you thought the speed of writing code was your problem - you have bigger problems"
And some comical turns of phrase as well :-)
Link shared here earlier by @RuthMalan - thanks!
(I don't know if Andrew Murphy the author is on Fedi?)

AI coding tools are optimising the wrong thing and nobody wants to hear it. Writing code was already fast. The bottleneck is everything else: unclear requirements, review queues, terrified deploy cultures, and an org chart that needs six meetings to decide what colour the button should be.
Most organizations have no problem with output, but rather with responding to signals. This is a problem because when t(decision) > t(production), the system becomes structurally disconnected from reality. It is completely worthless to deliver faster if decisions take too long, because then any knowledge gained is immediately devalued.
A thread 🧵
#SystemsThinking #WorkFeedbackLoop #Flow #TheoryOfConstraints #DecisionLatency
(1/2)
Revolutionizers Bundle https://leanpub.com/b/revolutionizers by Edward W. Barnard is the featured bundle on the Leanpub homepage! https://leanpub.com #ComputerProgramming #Ai #SoftwareEngineering #TheoryOfConstraints #ComputerScience #Education #Gpt
The Revolutionizers Bundle brings together all four books in the series, plus two free companion essays, into one integrated exploration of how ideas evolve, how technology transforms, and how everyday people can become innovators.
Find it on Leanpub!
It's worth reminding a lot of AI folks that:
Time saved by optimizing a non-constraint is not time saved for the whole system. It's not only time not saved, it's actually reducing the throughput of the whole system.
So, "saving time" in a non-constraint - doing that which should not be done in the first place - deteriorates the performance of the whole system.