I learned what sells. Then I learned to build.
Before writing software, I spent twenty years selling. It taught me to listen for the problem underneath the request, and to notice when a polished presentation had no useful answer behind it.
The question stayed the same
Learning to design and code changed the tools, not the question: what would make this useful enough for someone to choose it? I am self-taught, and the work keeps teaching me.
The whole system interests me
A thoughtful interface is satisfying. So is an API contract that prevents a bug, an offline queue that saves someone's work, or a deployment that is easy to recover. I like the points where design decisions and engineering decisions meet.
Writing down the decisions
The articles and case studies on this site explain how I think through those tradeoffs. They are the best starting point if you want to understand how I might approach your product.