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
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.
Optimistic locking fails on the row you care about
Optimistic and pessimistic control aren't a performance preference, they're a claim about how writes are spread across keys. Production concentrates them on a handful of rows, which is where the optimistic bet loses, and where the better answer is often to stop having a contended row at all.
Double-entry as a data model, not an accounting concept
Every transaction sums to zero isn't accounting vocabulary, it's an invariant a database can enforce. What changes when the balance stops being a column you update and becomes a number you derive.
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