Software development is fundamentally an exercise in composition. We take big, complex problems and organize them into smaller, solvable parts. So the question isn’t whether you’re composing or not. It’s whether you're composing with intention.
We aren’t here to rehash “composition vs inheritance” or preach about the dogmatic use of the latest architectural trend. Instead, we’re going to explore the thought process that goes into structuring and designing code so that you spend less time writing, less time reading, and less time debugging.
In this presentation, we will cover a practical three-step process for designing readable and low-friction systems:
* Split responsibilities to reduce complexity.
* Strengthen interfaces for wide applicability.
* Connect components to improve maintainability.
This talk equips you with the skills to manage your cognitive budget even when you're facing developer fatigue, mounting technical debt, or AI-generated bloat.
Let’s stop being afraid of our own codebases.
