My latest blog "if it hurts, do it more" covers my experience making changes to engineering teams at Canonical over the past 5 years.
Engineering teams are complex, and it's easy for things to slip between the cracks. This post covers an approach that I've found useful for building competence in teams around certain kinds of tasks.
A bit of a break from the usual engineering content around #Ubuntu, but very relevant to how things are getting done behind the scenes!