Early on, I was drawn to programming because it felt fairly straightforward: inputs, outputs, logic, control and tons of fun. Experience made that view more honest. Building software in the real world turned out to be a lot more complicated than I thought; changing requirements, rough edges in tools, ambiguous communication, and brutal systems that do not care about your niceties. I grew to embrace that and the discipline that comes with turning uncertainty into something usable.
Over time I have become less interested in complexity for its own sake and more interested in software that is durable, legible, and honest. I like systems that can be understood, modified, and trusted. I like writing that explains the reasoning behind a decision, not just the decision itself. I like codebases where the next person can tell what matters and where to look.
What I have learned, more than anything, is that software development is a practice of continuous refinement. You refine how you model a problem, how you communicate tradeoffs, how you debug, and how you decide what not to build. That is the kind of work I want to keep doing: building useful systems, learning in public, and getting steadily better at making complex things feel clear.