Software Architecture: The Bad Parts
Description
In this talk, I will demonstrate how so-called good practices combined with a shallow understanding of the domain can create a dangerous illusion of control.
Using a real-world example from the Connected Health domain—specifically, liver cancer risk alerting—I will show how a noun-driven design approach leads to excessive coupling and brittle systems.
The talk will explore common architectural pitfalls such as context violations, database coupling, domain leakage, and mixing read and write models. I will also challenge a popular industry belief by explaining why Clean/Hexagonal Architecture is not an architecture.
Attendees will leave with a clearer understanding of how design decisions shape system behavior—and how easily “best practices” can fail when the domain is misunderstood.
The talk is based on this article.
I’ll be presenting the Miro board and Visual Studio Code. Tech stack is NodeJS/TypeScript/PostgreSQL.
Bio
A software engineer with 15 years of experience, currently working as a hands-on Solutions Architect and consultant, helping development teams deliver better products. He focuses on collaboratively designing solutions with clients—evaluating ideas, assessing risks, and translating them into technical requirements aligned with business goals.
Software Architecture: The Bad Parts
Description
In this talk, I will demonstrate how so-called good practices combined with a shallow understanding of the domain can create a dangerous illusion of control.
Using a real-world example from the Connected Health domain—specifically, liver cancer risk alerting—I will show how a noun-driven design approach leads to excessive coupling and brittle systems.
The talk will explore common architectural pitfalls such as context violations, database coupling, domain leakage, and mixing read and write models. I will also challenge a popular industry belief by explaining why Clean/Hexagonal Architecture is not an architecture.
Attendees will leave with a clearer understanding of how design decisions shape system behavior—and how easily “best practices” can fail when the domain is misunderstood.
The talk is based on this article.
I’ll be presenting the Miro board and Visual Studio Code. Tech stack is NodeJS/TypeScript/PostgreSQL.
Bio
A software engineer with 15 years of experience, currently working as a hands-on Solutions Architect and consultant, helping development teams deliver better products. He focuses on collaboratively designing solutions with clients—evaluating ideas, assessing risks, and translating them into technical requirements aligned with business goals.