More software engineering leaders need to remember Parkinson’s law of triviality AKA bike shedding.
It's the tendency of humans to spend disport large amounts of time on things that do not matter.
Where does this show up in software engineering?
- code review
- sprint retrospective
- root cause analysis
How does it show up?
- formatting for PR titles
- rigid guidelines for user stories
- new runbooks for each outage ever experienced
1/2