Below are my notes on software design and process. Some of them are reordered under the title Meaningful software in a way more suited for sequential reading here.

Principle of dead man walking


A software project is nothing like a living being. As long as you holding it together, it is a dead man walking. Whenever you stop, it falls apart back into a heap of limbs, which may still move in a life-like Brownian motion. But if continuously held, it will get to the finish line, which most of the time is all that required.

And rather do not flatter yourself: a software project is not a marionette, and even more so you are not a puppet master.


16/11/2018, Myth of Scrum team

24/10/2018, Principle of root cause of success. 5How

23/08/2018, Prioritizing backlog items: a checklist

22/08/2018, Software team collapse: game of jenga tower

11/05/2018, Principle of dead man walking

28/03/2018, Software project collapse: modeled after motor neuron disease

29/01/2018, Deployment bias

25/01/2018, The third skill

31/07/2017, Don't reply e-mails and other communication tips

16/12/2016, Modeling bias

28/11/2016, Preserving capabilities

22/09/2016, Principle of two extremes: no golden middle

05/08/2016, Give me everything

15/07/2016, Bugs and weeds

2013, Software engineering and humanities

2013, Code as two texts

2013, Architectureless design

2013, Staying in touch. Performative negotiation

2013, Matter of scale

2010, Principle of inverse encapsulation