01mehrshad
About
Backend engineer (~5 years .NET). Clean Architecture, security, and systems that hold up at scale. Personality between INTJ and ISTJ — S and N at 50/50.
This blog is where I work things out in public, rabbit holes included.
at a glance02
03who i am
I'm a curious systems-builder with a mild obsession with understanding how things actually work. I gravitate toward complicated things — not because I enjoy complexity for its own sake, but because I get uncomfortable when something feels like a black box. I want to know what's underneath it, what the trade-offs are, where it breaks, and why people made the decisions they did.
I'm naturally analytical, skeptical, and fairly independent-minded. I don't enjoy accepting something as "best practice" simply because everyone else does; my instinct is to ask why, then see whether the answer survives scrutiny. And I'm more of a builder than a performer — I'd rather quietly become good at something than convince everyone I'm already good at it.
I also have a tendency to go down rabbit holes. A simple question can become a three-hour investigation; a small project can turn into an exploration of an entire ecosystem. It is both one of my strengths and one of my recurring problems: the curiosity sometimes expands the scope faster than the ability to finish it.
I don't just want to know what works. I want to know why it works, why it might stop working, and whether I can build a better version myself.
how i work
Analytical, independent, future-oriented — somewhere around INTJ with strong INTP tendencies. I like having a direction, and I enjoy questioning that direction once I understand the problem better. I care about competence, sometimes more than I should, which also means I can be overly critical of my own work: "good enough" is difficult when I can clearly see how something could be improved.
what i build
I'm not purely theoretical. Ideas become much more interesting to me once I can turn them into something tangible, experiment with them, break them, and rebuild them. I have a strong preference for control and understanding over convenience: abstractions and managed services are fine when they make sense, but I want to know what I'm giving up in exchange. I like tools that are transparent, composable and replaceable rather than systems that lock me in.
outside the editor
Late night, dark UI, a Linux terminal, too many browser tabs, coffee, a half-finished project, and one rabbit hole that was absolutely not supposed to take six hours. A technology I meet today can send me into documentation, source code, benchmarks and architecture discussions before the day is out.
curious · analytical · independent · builder-minded · skeptical · systems-oriented
résumé
A concise overview of my background, skills, and experience as a backend engineer.
reach me04
Replies go to whatever address you leave in the form; nothing is sold or added to a list.