What way can teams get into trouble? How do you resolve issues and sustain high-performing teams?
An opinion column for developers. Brutally honest, no pulled punches.
What way can teams get into trouble? How do you resolve issues and sustain high-performing teams?
Why do writing more code and working more hours fall short of delivering more value? What should engineers be doing?
Which software terms are so offensive that we should change them? How do you choose a good alternative to an offensive term?
What are the common mistakes when switching to DevOps? How can your team smoothly transition to DevOps?
How can good communication save you grief? What does a communication plan look like for rollouts, reorgs, and outages?
When is being lazy advantageous? Why not always jump into problems, work and team assignments, and new projects?
What purpose does a root cause analysis serve for incidents? Why ask why so many times?
What’s wrong with designating feature work as good, bad, and ugly? How should you categorize feature work and why?
Why do multi-team postmortems often devolve into blame games and inaction? How do you run a 90-minute postmortem in which every person and topic is heard, and owners are assigned to improvements?
Why are war rooms needed? What are the mechanics of running war room?