I feel much more software documentation could greatly benefit from this approach. Describing the "why" and design tradeoffs helps me grok a system far better than the typical quickstart or tutorials which show snippets but offer little understanding. That is, they rarely help me answer: is this going to solve my problem and how?
That is the structure they (any many others) are following :).
BTW your blog is probably the most pleasant looking website I've seen in a month at least to my eyes on mobile.