I follow the excellent John Cutler on Twitter. He regularly tweets thoughtful remarks on product development and has a talent for creating hard-working diagrams. The picture below shows the danger of focusing on near-term productivity.
John’s tweet struck a chord because less than 24 hours earlier I had given an internal presentation on a related topic at our regular All Employee Meeting. Although I wasn’t talking about Lean Product Development (it was a broad audience) I had stumbled onto some interesting and related research into psychology and mental health that I wanted to share.
The rest of this article…
Earlier this year a former colleague asked me to make a list of some of the books I’d recommended him over the prior months. I ended up really enjoying the exercise; it showed that I’d read more than I thought, and that plenty had made a significant impact on how I think and work.
I’ve definitely not completed everything below (and I’ve certainly missed a few books also) but it’s a good starting point. I’d love to hear what others think!
I put books into the following categories
I asked our CTO, as part of preparing this content for a conference presentation, about what he thought was interesting about our use of Kubernetes and he replied:
Teams don’t realise how much they haven’t had to do.
His comment was inspired from having recently read Factfulness: it’s harder to notice smaller but continual improvements and we consequently fail to recognise the progress we’ve made.
Our move to Kubernetes is significant though.
We created Kiam in 2017 to quickly address correctness issues we had running kube2iam in our production clusters. We’ve made a number of changes to it’s original design to make it more secure, reliable and easier to operate. This article covers a little of the story that led to us creating Kiam and more about what makes it novel.
I suspect like many users of Kubernetes we are in the process of moving lots of small…