Age 13 — understanding what developing means📋

Around thirteen, something clicked. I stopped thinking about "writing code" and started thinking about developing: taking a fuzzy problem from the real world, exploring its problem space, and dissolving it into composable units that could be assembled into a solution. Decomposition, composition, abstraction — I didn't have the vocabulary yet, but the intuition was there. That shift, from typing instructions to modelling problems, is the one I still rely on every single day as an architect.