2 ms·
- Start by making sure the ones committing Code to are also the ones getting called at 2 AM if there is a Production problem. - Get metrics the reward teams wi
by belter 5y ago
- Start by making sure the ones committing Code to are also the ones getting called at 2 AM if there is a Production problem.
- Get metrics the reward teams with Stable and Reliable systems, and avoid metrics that just reward teams that commit the most features
- Make sure the code reviewers have skin in the game, and that what they allow to pass reviews is also theirs to fix, not the the original coder.
- jnxx 5y agoHow would you do that in an area where release cycles are slow, like embedded software or industrial automation?
- belter 5y agoThe same way but slowly. Although technical debt in embedded software or industrial automation sounds like an explosive mix:-) Words you dont want to hear in the same phrase: "Life Critical" and "Technical Debt";-)