Streaming pipelines
Moving and shaping high volume event streams. Windowing, ordering, backpressure, and the late data that breaks all three. Kafka and Flink class problems.
Junior software engineer at Uber, working on backend systems like streaming pipelines, parsers, and OLAP query paths. Outside work I build my own apps.
role
Junior Software Engineer @ Uber
building
Murmur, a voice notes app I control
learning
Game dev and turning side projects into a business
Details stay home. The shapes of the problems do not.
Moving and shaping high volume event streams. Windowing, ordering, backpressure, and the late data that breaks all three. Kafka and Flink class problems.
OLAP serving where the answer has to be fast and fresh at the same time. Pinot and Hive class storage, indexing, and query planning.
Turning text into structure and back. Lexing, grammars, tree walking. Code where you can prove it works.
Go and Java services with clear boundaries and contracts. I like systems that stay boring, because boring means the pager stays quiet.
I had a problem and the existing options annoyed me, so I built my own. Each of these is used daily by exactly one user, me.
personal use, not launched
Voice notes apps were either too expensive or owned my data. I wanted both cheap and mine, so I built it.
personal use, not launched
Every practice tracker I tried wanted a subscription for a simple log. Mine lives on my own server.
Guitar
Playing, and logging it with Guitarix
Gym
Lifting. Progressive overload applies to code too.
Game dev
Dabbled a little
Reading
Economics, maths, systems