Currently exploring
Backend and platform engineering, distributed systems, and reliability. These are the questions guiding what I learn and build next.
Distributed systems
What if the work succeeded, but the reply disappeared?
I'm exploring how retry identity, durable state and acknowledgements fit together. A useful test is being able to explain what happens before and after each failure.
Platform engineering
How can one reliable boundary support several callers?
I'm interested in APIs and tools that make the safe path easy to use. That includes clear validation, useful errors and shared rules that hold across different interfaces.
Reliability
What should keep working when a dependency doesn't?
I'm learning to make failure behaviour explicit: timeouts, bounded retries, useful diagnostics and recovery. Small, reproducible failures give me something concrete to reason about.
I'm currently at Shopify and incoming at Stripe for summer 2027. I want to bring what I've learned about data systems, validation and backend services to infrastructure that other engineers depend on.
As I work through these questions, the smaller observations will go into Engineering notes.