Optimal PR size is
one line of code change that is reviewed immediately.
»Trunk Based Development and Pair/Mob Programming are not the goal per se
but an inevitable consequence of a desire to drastically tighten the feedback loop to review and integrate the code and ideas.
»Make your Pull Requests so small
that you annoy reviewers so often that they just give up and join you in a pairing session instead.
»WIP ⇆ waiting times
Long waiting times in the system incentivize increase in WIP.
And, the higher the WIP, the longer the waiting times will be.
When you reduce the queue time
processing time will get shorter as well because the feedback gets incorporated faster.
»Every change is a loss for someone
Shift in “outcomes over outputs” takes away power from people that used to have monopoly on defining solutions and next steps.
»Every long feedback loop
is (most probably) caused by:
»It's not about sharing the same database that's a problem
One more in “it’s not about X. It’s about about Y” series.
»It's not about long-lived branches that's a problem
It’s not about long-lived branches per se that’s an anti-pattern. It’s about coding in isolation for too long without getting the feedback.
»Event Sourcing and cheap storage space as enablers of ever higher scalability
Maybe late to the party, but just realized an interesting interplay between Event Sourcing and ever cheaper storage space.
»