Why Methods Work

My theory is that the secret code for most self-improvement systems [is that] any idea that helps you to become more self-aware can usually help you to reach a goal or affect a favorable solution. [...] I think the idea basically stays the same; listen critically, reflect honestly, and be circumspect about choosing the parts that comport with your needs, values, and personal history. [...] the secret is to watch your progress and just keep putting one foot in front of the other [and to] stay focused on achieving modest improvements in whatever you want to change. Small changes stick.
- Merlin Mann, “Systems, ciphers, and the dirty little secret of self-improvement,” 43 Folders.

As a programmer, working equals thinking. Outside work, I read a lot and think a lot. So whenever I do the laundry, for instance, or cook, clean the house – or, which is something I’m doing right now, make preparations for painting the walls in our new office – I think about how immediate feedback is. Nobody would devise a method for making your bed, as improvement happens automatically.

When preparing the renovations of our office, many of the things are repetitive, monotonous tasks, and for every repetition you find out ways to get more efficient. For instance, I’ve covered the wooden roof beams with paper to protect them from dripping paint. The first time I cut some paper, then wrapped it around the beams. After a while, it became natural to cut several sheets of paper in advance, which took less time as I didn’t have to switch tasks so often.

When developing software, feedback isn’t as immediate. Method doesn’t come as naturally. People stick to inefficient ways of doing things for ages. To self-improve you need self-discipline.

My suspicion has been, and Merlin confirms it, that paying attention is what matters.