I came into development from graphic design, and it still shapes how I work today. I see not just the architecture and the types, but how a decision will land for the end user — where they'll stumble, what will slow them down, which interface they'll call "intuitive" without knowing why.
I've spent the last eight years on airline booking systems. It's a domain where mistakes are expensive: hundreds of fare rules, passenger data validation, heavy search queries that have to be cached without breaking. You can't just "patch it and forget it" here — you need an architecture that holds up under growth.
Alongside that, I publish open source. For me it's the best test of engineering quality: code you can install from npm, read, and reuse. Modest in scale, but honest in substance.
