I will not install your language tools

I have a principle now: no installing languages or tools or any project-specific stuff on my laptop. Only Docker. Every project can happily have its own version of Ruby or Python and their dependency managers. When my laptop gets lost again, I won’t spend (as many) weeks being surprised by what I need to install again.

Here is my tiniest intro to using Docker for this purpose. Not for production, but for my purposes. And for making projects work-on-able by other people on every operating system.

Find it on RubyTapas:

Learning as becoming

businesses… need a new worldview… that shifts the emphasis… from success as accomplishment to success as learning.

Jeff Sussna, in Designing Delivery

“Success as learning” doesn’t mean learning lessons. This is not learning as facts.

This is learning as becoming. It is learning that bakes into who we are and how we do things, bakes into people and software.

Success is becoming a person, a symmathesy, an organization that can do more than before.


I am locally very important, globally not important.

It helps that I’m not important, that the world moves on whatever I do, it doesn’t need me to push it

The people close to me, they count on my help. Local systems, my family and my team, what I do matters to them. Failing them, this hurts. It is okay that it hurts.

I want to make a big difference to my family and team, and small differences in the world.

There is a wrenching drumb in my chest today
It squeezes in a nearby beat
Walk with it into a new self, a new world.

The artifact and the process

again: Every action has two results: a set of side effects on the world, and the next version of ourselves.

Sometimes in the creation of an artifact, the artifact itself is less important than the process of creating it. Wardley Maps are like that too – it’s about the thought that goes into creating them, and the conversations they enable. (video by @catswetel)

Most diagrams, especially on the white board, communicate very well to the people who participated in their creation, and very little to anyone else.

It’s the co-creation that matters. The participation in creating the artifact. The output is the next version of our team, with this common ground we established in the process.