Software Engineer
Rasikh Mashhadi
I build the quiet parts of the stack. Loud in impact.
What I work on
Clean architecture
Boundaries that hold. Domain logic that doesn't know which database it's stored in, so it outlives the one that replaces it.
Scalable systems
Correct first, then fast. Systems that keep their invariants under load instead of discovering them in an incident review.
Developer experience
The build, the types, the local setup. The work that quietly makes every other piece of work cheaper.
Approach
With a focus on clean architecture and long-term maintainability, I bring ideas to life through thoughtful code, scalable systems, and strong developer experience.
Every line of code is an investment in the future: designed to evolve, not just work.
This site is a quiet space for thoughts, experiments, and things I'm building. No noise. Just software.
A digital garden where ideas take root and grow into something meaningful.
Writing
Feature flags are a debt instrument
A flag is a branch you have promised to delete, and the old side keeps rotting after the rollout ends. What an empty flag store did to a recovery region, and why every flag needs an owner and an expiry date on the day it is created.
The reconciliation break that was correct
A break has three possible culprits, and the comparison is always the cheapest one to blame. What happened when a team fixed the reconciler to make fourteen lines go away, and why two of them should have stayed.
The calendar is reference data, not a utility function
Every date that decides what money does comes from a calendar someone else owns, with its own holidays, its own weekend and its own cut-off clock. What changes when you stop computing business days and start storing them.
Elsewhere
Working on something in the same territory, where systems have to be right and stay right as they grow? I'm easiest to reach here.
LinkedIn