Every software project is a series of decisions: about architecture, design, what to prioritize and what to postpone (or ignore altogether). And behind every decision is a trade-off, between performance and complexity, scalability and simplicity, pragmatism and purity, short-term delivery and long-term maintainability.

In this talk, I’ll walk you through real-world examples of architectural and design choices I have made in the past. Some were made under pressure, others based on team dynamics, technology constraints, or simply the information I had at the time.

You’ll get to see the trade-offs behind decisions. We'll also look at the impact of team maturity, client capabilities, and deadlines. Because context is everything.

And here’s the twist: you get to be the jury. Was this a solid decision given the constraints, or an architectural blunder waiting to happen? Rate my decisions, and let’s explore what we can learn from them. In the end, we all want to get better at designing systems that can stand the test of time and change.

The audience and myself need internet.