One of the most formidable obstacles in software architecture isn’t the technology itself—it’s the resistance you face when introducing something new. Sometimes we need to evolve, other times we need to revolutionize. And yet, even when the writing is on the wall—when the old system is
One of the stark realities in software development is that technical decisions often come from people with minimal software engineering background. While cross-functional collaboration can be beneficial—even essential—there are moments when it morphs into an “intrusion.” You’ve probably experienced the frustration of a non-technical manager dictating
Pick up any software architecture book, and you’ll see detailed discussions about microservices, event-driven paradigms, domain-driven design, and other foundational concepts. What you often won’t find is how to navigate the intricate, sometimes frustrating organizational politics that can derail even the most well-intentioned design. In this
If you’ve ever dived into software architecture books or blogs, you’ve probably come across in-depth discussions on microservices, event-driven architectures, domain-driven design, and more. You’ll learn about best practices, the right patterns to use in the right situations, and tips for structuring large-scale systems. Yet, there’s
The parallelism between the decline of big empires in history and the constant delivery of high-quality (software) products.
Why writing about the dark side of software architecture and what is it about?
