About
How I got here
It started with games. I was fascinated by computers as a child, and the more I used things like Google, Facebook and YouTube, the more I wanted to know what was behind them — how the web actually worked, and how systems at that size get built at all. During my Bachelor’s that curiosity turned into the thing I wanted to do for a living.
I still think it is the most interesting question in the job. Every system I have worked on is somebody’s answer to it, and the answers are never obvious.
Since then I have worked on distributed platforms and on enterprise business systems — two fairly different shapes of problem, with different things to get wrong. Where and what is on the home page.
What I am working toward
- Backend depth. Designing systems that are scalable, reliable, maintainable and performant, and getting sharper on the trade-offs each of those goals costs the others.
- Software architecture and technical leadership. Owning the design decisions rather than only implementing them, and guiding a team through them. I am not there yet; this is the direction I am deliberately heading in.
- Sharing what I learn. Through writing, and through helping other engineers where I can.
Why I write
Writing is how I find out whether I actually understand something. If I cannot explain why a decision was made and what it cost, I did not understand the decision. Putting it in public also means the reasoning can be checked by people who know more than I do.
Most of what I publish is about .NET Core, architecture patterns, databases and performance. You can read it here.
Get in touch
If any of this overlaps with what you are working on, I am glad to talk.