4 ms·
Ultimately it's about maximizing the productivity of the team or engineering organization at large more than it is about optimizing the productivity of a single
by nilkn 7y ago
Ultimately it's about maximizing the productivity of the team or engineering organization at large more than it is about optimizing the productivity of a single developer. This often means that it's worth creating a mild disruption for individuals if it prevents the team from falling into a dis-coordinated state that can take days or weeks to recover from.
- JamesBarney 7y agoWhat is being communicated that's saving the dev teams weeks of time?