The C4 Model: what I draw, and what I stopped drawing Four levels of diagram for explaining a system. Its real use to me was deciding what not to draw, which is where a client's time and money go missing. Architecture 16 sept 2026 Books
Vector Databases: the answer is usually the database you already run A book defending an unfashionable position: you do not need a new database to search by meaning, an extension on the one already in production will do. I agree, and it still has two problems. AI Architecture 5 sept 2026 Books
Thinking in Systems: the number they ask you to change is rarely the problem The best thing I read this year about why companies resist improvement. Its list of leverage points explains, better than any methodology, why so many projects change everything and change nothing. Architecture Strategy 30 ago 2026 Books
The Definitive Guide to DAX: the model decides the measure Seven hundred and sixty-eight pages on a calculation language that looks like a spreadsheet and is not. The lesson I keep is not about syntax: when the data model is badly built, every measure fights it. Architecture Craft 8 ago 2026 Books
Software Architecture, The Hard Parts: there are no best practices, only trade-offs The book opens by claiming that architecture has no best practices and spends four hundred pages teaching how to compare alternatives. That is the skill, and almost no book teaches it. Architecture 27 jul 2026 Books
The Software Architect Elevator: the summary holds up better here, and still loses the best part Another paid summary, and this time the format suffers less: the book is built from short essays whose titles carry the thesis. Even so, what makes Hohpe worth reading are the anecdotes, and that is exactly what a summary throws away. Architecture 11 jul 2026 Books
The amendment that moved the deadline up and killed the transmission window A month after the previous one came its amendment: the deadline moved from the tenth to the seventh, and the few-day window for transmitting a document disappeared. That second part changes system design, not procedure. Architecture Craft 5 jul 2026 Books
Odoo 19 Development Cookbook: a good cookbook, and what is missing from it Twenty-three chapters of recipes for the new version. It is the book I keep open while working, and the hole it leaves is exactly the problem I get hired to solve. Architecture Craft 20 may 2026 Books
Mastering ArchiMate: I kept the discipline and dropped the notation A thick, opinionated manual on the standard language for drawing enterprise architecture, including its criticisms of that language. I use its rigour daily and deliver not one diagram in that notation. Architecture 7 may 2026 Books
Mastering API Architecture: contract first, test second Designing, testing and operating the interfaces between systems. It left me two habits that changed how I write an integration and how I charge for one. Architecture 4 may 2026 Books
Learning Serverless Security: the permission is the blast radius A lab book: you break applications on purpose across three clouds and then fix them. Reading it without doing the labs only half works, and it still left me a rule I apply to any deployment. Architecture 22 abr 2026 Books
Learning Domain-Driven Design: what deserves custom code and what does not The best way in to domain-driven design I know. The first half I use every week; the second is written for a kind of software that is not the kind I work on. Architecture 16 abr 2026 Books