Culture
On Failure and Organization Resilience 3 minutes read.
This is how you celebrate handling & learning from failures while creating a safe environment that appreciates org growth: "So pleased to have won this year's Three-Armed Sweater Award for that time I accidentally upgraded Apache!" -- while Etsy is going through some changes these days, I'm sure that the people and culture will help them in this transition. This paragraph says it all: "It was a beautiful scene of empathetic and coordinated chaos. People were using Slack to coordinate, to figure out what the status was and what still needed to be done and to just help do it. People who arrived a few minutes late to the scene didn’t jump into asking who’s "fault" it was, because that’s not how we roll, they just wanted to know what was going on and how they could help."
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
What Can Developers Learn From Being on Call? 4 minutes read.
I'm a big fan of all developers being on-call, at least to some degree. You simply cannot teach people to build robust and reliable systems without feeling the pain themselves. You cannot talk about concepts such as self-healing systems or introducing failures by design without getting the people who build it to wake up at night and understand why it matters. Don't outsource this skill too quickly.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
The PM Mind Meld: How Do You Keep the CEO and PM on the Same Page? 5 minutes read.
If you want to feel you're moving in the right direction as a company, this is a must read and a must share with the relevant people. I said "feel" because people need to feel that the CEO/PM get their input in, but above all, they'd like to hear the story, the vision. The need to feel connected to it.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.