I have never been particularly interested in answers. Answers are where curiosity goes to die. The interesting part is the unanswered question.
I build software, study complex systems, and spend an unreasonable amount of time chasing problems that refuse to stay solved.
Most of my work sits somewhere between engineering and research. I enjoy the moment when a system stops being a collection of technologies and reveals itself as a puzzle: an algorithm that scales poorly, a bottleneck nobody can explain, a mathematical property hiding in plain sight, a design that almost works.
Those are problems worth keeping.
What I Work On
My interests tend to orbit around performance, scale, and understanding how systems behave.
Some recurring themes:
- Software architecture
- Systems programming
- Parallel and distributed computing
- High-performance computing
- Algorithms and optimization
- Computer vision
- Embedded systems
- GPU acceleration
- Performance engineering
- Mathematical modeling
- Research and experimentation
At any given moment, I am probably reading papers, profiling code, building prototypes, or disappearing into a rabbit hole.
The technology changes. The questions rarely do: