Most of my days go into Spark, fixing jobs that are slow, expensive, or failing every night. I’ve cut resource usage on some by up to 90%, then built tooling so nobody digs through those logs by hand again.
Outside work, I’ve contributed to Apache AirflowContributor, maintained
CRI-OMaintainer and
DuckDuckGoMaintainer, and did
Google Summer of CodeStudent with TEAMMATES at NUS.
When a problem annoys me enough, I turn it into a tool, like spot-optimizer (11k+ downloads) or uv-bundler, and I write about Spark internals, databases, and functional programming.
Always happy to talk data, open source, or side projects.
System design practice that judges your decisions, not your diagram. Each problem gives you real requirements and an empty canvas. Every box you add gets a verdict: right-sized, overkill, or about to break, with the reason why.
Pass, and a Deep Dive raises the bar, just like an interviewer would: more traffic, users worldwide, a database node that dies. Your design has to keep up. Stuck? Get a hint first, then watch the reference design built box by box.
Try Litmus