About
On engineering
I'm currently a Java developer at Velocity Tech. Before that I was at Bose, where I worked on audio systems — close tolerances, signal chains, and hardware that has to behave identically at scale. That experience taught me that the gap between a spec and a shipping product is where all the interesting engineering lives.
My personal obsessions are Rust (for the clarity it forces on you) and Python (for how fast it lets you think). I'm drawn to robotics, distributed systems, and anything that sits at the boundary between software and the physical world.
On learning
I learn by building things slightly above my current level. The discomfort of not-knowing is the signal, not the problem. I read papers when I want to understand something from first principles, and I read blogs when I want to understand how someone actually implemented it at 3am under pressure.
Lately I've been going deep on distributed systems consensus algorithms, transformer architectures from scratch, and the robotics middleware stack.
On spirit
I think consciousness is the most interesting problem that exists and is currently receiving the least serious attention relative to its importance. I meditate inconsistently, read Krishnamurti and Ramana Maharshi, and find that the questions these traditions point at are the same ones lurking underneath all serious engineering work.
What is attention? What is awareness? What is the observer? These aren't just philosophical questions — they're engineering questions about the nature of systems that observe themselves.
On building
I build things because the act of making something real — something that works, that has edges and constraints and properties — teaches you things that reading never can. The project is often the excuse; the learning is the point.
I'm particularly drawn to systems that operate at physical boundaries: robots touching the world, audio hardware pushing signal-to-noise limits, interfaces that try to disappear. The constraint makes the design.