A short, sad story about high transaction cost causing inevitable big batches and long feedback loops
The longer it takes me to test/check a change ->
»Having a need for coordination
and a corresponding role is likely an indicator of a process focused on utilization (busyness) instead of flow (eliminating queues and wait times).
»Optimize your code for explicitness
Two super simple examples, achieving the same thing.
»When it's too difficult to measure the whole system
in order to improve it, the second best thing that feels natural to do is to improve what we can measure.
»The Theory of Constraints and Amazon
Not sure how much it’s known, but Jeff Bezos is a huge fan of the Theory of Constraints. Such a big fan that ‘The Goal’ from Eli Goldratt is one of the 3 must-read books he gives out to all senior executives joining Amazon.
»When I have a fast test suite
I’m able to experiment with the production code.
»People don't do big changes
because they like them better than smaller changes.
»Quality and the failure of the process
When you co-create as a team (together and at the same time) “quality is everyone’s responsibility” mindset is inherent and you don’t have to keep reminding people of it.
»What is the cost of a very low defect/mistakes rate per unit of time?
The “cost” is increased speed.
»The amount of mobbing during development
tends to be inversely proportional to the amount of mobbing needed during outages.
»