Introduction
Tech Lead and Senior .NET Developer with a long-standing passion for building software. This blog documents lessons learned, technical discoveries, and recurring problems encountered while working across the .NET ecosystem, Go, Docker, microservices, and modern web development.
By Dom Reilly · Posted 07 Mar 2026 · 3 min read
Who am I?
At the time of writing this post, I'm a Tech lead and senior developer working with the .NET platform (framework and core) on a daily basis.
I've been interested in programming for a long time, and created my first website in Microsoft Frontpage(who else misses WYSIWYG editors?!), moving on to PHP to build a text-based multiplayer RPG, then to .NET framework during university.
Since then, I've pretty much stayed in the .NET ecosphere with some divergence into branches of .NET like Xamarin to do mobile app dev and webforms when maintaining legacy solutions.
In my spare time, I enjoy expanding my knowledge into new topics - most recently this has been: Go, Docker, Microservices and some Blazor 10 to refresh myself.
Why did I make this?
I wanted to see how difficult it would be to create a blog using Blazor, especially as I hadn't used it in anger since .NET 6, I was keen to test it out! (spoiler, I ran into a lot of issues when trying to use RCL and make a generic class library, with the vision to making this open-source)
My first attempt at the project started using Vue.JS and Web API, to refresh myself on .NET outside of Blazor and MVC, but I quickly realised that wasn't the tool for me and switched to Blazor.
My second attempt came after many months away from the project - I had hit the dreaded wall of doom and didn't have the motivation to continue.
I'd been playing with Go for a few months and decided that I should switch the backend out for a go-based API supported by a MySQL database.
Roll on a few weeks and I enlisted the use of Codex to help me migrate it, because:
A) it seemed like a good way to start practicing using Codex
B) I didn't think I could face the manual migration
Finally, we got to the end of the migration, and I was able to release both platforms, which then allowed me to write this blog post that you're reading!
What are you planning on using this platform for?
Over my career, I've found myself writing the same code repeatedly, or running into similar, if not the same, issues - because of this, I've decided that creating a blog to store this thoughts and discoveries would be beneficial, more so for myself to refer back to, but if they help anyone in the slightest, then all the better!

Keep reading
Related articles
The Most Valuable Column Nobody Thinks About
While investigating some unexpected data, I was reminded of a lesson that's followed me throughout my career: timestamp columns never seem important until the day you need one. It's a small design decision that...
AI Assisted Development: You’re Not Behind, But It’s Time to Start
AI is becoming part of the modern developer workflow, but it is not replacing developers. This post explores how I’m using AI to reduce friction, generate tests, sanity check ideas, speed up repetitive tasks, and learn...