Over the years, I came to realize that usage of some test doubles and popular patterns in test code can actually be an indication of a deeper design problem in production code.
»chances are you’re used to making big changes.
»Sure, until you realize that the tool is influencing the mindset as much as the mindset is influencing the choice of the tool.
»is to invest in making experimenting and trying out ideas cheaper in order to sooner bring relevant data that can inform our decisions and reduce uncertainty as to what to prioritize and where to invest.
»is a poor man’s try of achieving predictability while eroding trust and jeopardizing psychological safety.
»and 1 hour to get a review and PR approval, that means the wait to processing time ratio is 60/5=12, and flow efficiency is only 7.7%.
»With Pull Requests you see just a polished and thought-through end result.
»if everyone that is needed is immediately available to respond (by #mobprogramming for example)?
»for reviewing their PRs (or any other help they need), your problem is not people not prioritizing other people’s work and lack of “team player spirit”.
»by hiring more people, don’t be surprised to see the culture of ineffective parts of the organization eat away the culture of effective parts of the org, which doesn’t have a need to scale at such a rate.
»