Clarity before complexity
Code is read far more often than it is written. Obvious logic usually wins over cleverness.
How I think, work, and approach engineering.
I care about building software that is clear, useful and dependable.
My current work focuses on customer-facing assistants and the operational workflows behind them, combining frontend engineering, backend systems and practical AI.
I start by understanding the problem, then design the simplest system that can solve it well. From there, I build in small increments, make failures visible and improve based on real feedback.
The tools will change. The principles will not: clarity before complexity, reliability before cleverness and engineering judgement over hype.
Engineering Philosophy
Reliability before cleverness
Systems should fail predictably. Boundaries, retries, and operational safety matter more than novelty.
Systems should be observable
If you cannot see what your system is doing, you cannot trust it. Telemetry is a feature.
Engineering judgement
Automation amplifies capabilities, but foundational engineering understanding still sets direction.
How I Work
01
Understand the real problem
02
Map the constraints
03
Break the system into clear parts
04
Ship in small, useful increments
05
Make failures visible
06
Improve based on feedback
Current Research
MSc ResearchIn Progress
Self-healing backend operations agents.
Designing an AI-powered self-healing backend operations agent that helps production systems detect, diagnose, and recover from failures while keeping engineers in control.
The research explores how AI can improve reliability, observability, and operational resilience without sacrificing engineering judgement.
Outside Engineering
Strength
Strength
Strength training keeps me disciplined and grounded. The progression mindset maps well to engineering work.
Endurance
Endurance
Long-distance running gives me the mental space to think through complex systems problems away from the screen.
Community
Community
I care about learning with other builders, sharing ideas, and staying connected to people doing serious work.
Continuous Learning
Continuous Learning
I spend time studying systems, infrastructure, AI, and the mechanics behind reliable software.