Hey there,

I've spent so much time reading books this year and so little time processing what I have read. My way of processing a book is going through my notes and writing them up in a blog post. 

So, this week, you get my latest book notes, which are more inspirational in nature than the usual "Howto"-style tutorial. I hope you enjoy!

Cheers,

Tom

P.S.: If you have reached out to me via email lately, I didn't answer. Turns out that I had forgotten to copy the MX records when I changed DNS servers and I didn't receive any emails in the last two months. Please try again now. I was wondering why my inbox was so silent... .

And here are this week's links to other interesting topics I found:

• The purpose of software architecture - introduces a very succinct purpose of software architecture: the well-being of all humans involved.
• Technical Debt: Why it'll ruin your Software - an interesting discussion of tech debt and how to manage it.
• Diagrams as Code - Simon Brown tells us why "diagrams as code" is valuable. Personally, I think that "diagrams from code" would be even more valuable, but that's another story... .