Architecture

🪵 There’s a woodpecker on the cover of Software Architecture: The Hard Parts. Probably a coincidence – O’Reilly doesn’t pick cover animals to match the topic. But I like to imagine it’s a particularly determined one drilling into the same hard spot, over and over, until something gives – which is what got me thinking […]

AI is getting remarkably good at the HOW. It can generate code, propose architectures, compare design patterns, and automate implementation.That’s exactly why architects need to become even better at the WHY. If I could rename the role, I’d jokingly call it Problem Architect instead of Solution Architect. 🙂 Not because solutions aren’t important, but because

I really enjoyed rereading Chapter 12 of Software Architecture: The Hard Parts by Neal Ford, Mark Richards, Pramod S. and Zhamak Dehghani (O’Reilly 2022) this May holiday🌞. That chapter is about Transactional Sagas, and I couldn’t resist turning it into a short post 🙂. The authors take the forces of communication, consistency, and coordination and turn them

Really enjoyed reading 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐟𝐨𝐫 𝐅𝐥𝐨𝐰 by Susanne Kaiser over the Christmas holidays. The book clearly shows that combining #teamTopologies, #wardleyMaps and #DDD creates a synergy far stronger than any of them could achieve on their own. The key lies in connecting three dots that often exist in isolation:💼 Wardley Mapping → map your landscape

📣 Really enjoyed reading Software Architecture: The Hard Parts by Neal Ford, Mark Richards, Pramod S. and Zhamak Dehghani (O’Reilly 2022) as a natural follow-up to Fundamentals of Software Architecture. While Fundamentals introduces core concepts and laws of software architecture, The Hard Parts dives into the messy, trade-off-heavy situations that don’t have clean answers, especially