Modern software systems are no longer isolated pieces of code—they are complex, interconnected systems where small decisions can have unexpected consequences. This talk introduces systems thinking as a practical skill for developers. Instead of focusing only on immediate outcomes, we'll explore how design decisions create second-order effects: hidden coupling, team friction, performance bottlenecks, and long-term maintenance costs.

Through relatable examples, you'll learn how to:

1. Recognize feedback loops and unintended consequences
2. Design with dependencies, not just components, in mind
3. Make decisions that hold up as systems scale and evolve

If you've ever fixed one problem only to create three new ones, this talk will give you a clearer mental model for building systems that behave predictably over time.