I wanted to understand software architecture. Main reason is that so far, most of my coding was limited to independent scripts. And whatever I did beyond that felt clumsy. Furthermore, my past jobs, in between my coding lives, dealt with big pictures and making sure all parts had the data, knowledge and processes to work. Enter (software) architecture.

So enough background justification, here are my notes on the book, organised by its different parts rather by chapters.

Part 1: introduction