This is a place where I’ll share the things I learn, build, break, fix, and occasionally wonder why I ever started working on in the first place.

I’m a software developer, and most of my day-to-day work revolves around C#, .NET, APIs, databases, distributed systems, and financial technology. Over the years, I’ve learned that some of the most useful knowledge comes not from perfectly written tutorials, but from solving real problems — especially the problems that make you stare at an error message for far too long.

So, that’s what I want this blog to be about.

What You'll Find Here

I’ll be writing about things such as:

  • .NET & C# — architecture, performance, dependency injection, reflection, APIs, and the occasional strange framework behavior.
  • Backend development — building services that are reliable, maintainable, and hopefully less complicated than they need to be.
  • Databases — SQL Server, Entity Framework Core, performance, queries, and lessons learned from production systems.
  • FinTech — software engineering in financial systems, banking integrations, payments, and the challenges that come with moving money through software.
  • DevOps & infrastructure — Docker, Linux, CI/CD, deployment, monitoring, and getting applications from “works on my machine” to actually working somewhere else.
  • Architecture & engineering — decisions around designing systems, choosing between approaches, and understanding the trade-offs rather than blindly following patterns.
  • Experiments & side projects — sometimes the best way to understand something is to build a small project and see what happens.

And probably a few things that don't fit neatly into any of those categories.

Why Another Tech Blog?

Because I keep finding myself searching for answers.

Sometimes I find exactly what I need. Sometimes I find five Stack Overflow answers written in 2017, three GitHub issues, and a blog post that starts with “It's actually very simple…” before proceeding to make it considerably more complicated.

I'd like to contribute to the other side of that search.

When I solve something interesting, I'll try to document it. When I compare two approaches, I'll try to explain why one might be better instead of simply declaring a winner. And when I get something wrong, I'll hopefully document that too.

No Gurus. Just Learning.

I'm not here to pretend I know everything.

Software development changes constantly. Technologies evolve, best practices change, and solutions that made perfect sense a few years ago can become technical debt today.

This blog is therefore as much a record of my own learning as it is a resource for anyone else who finds something useful here.

If something I've written helps you solve a problem, understand a concept, or avoid spending three hours debugging the wrong thing, then the post has done its job.

Let's Build Something

Whether you're a fellow .NET developer, a backend engineer, someone working in FinTech, or simply curious about how software systems work, you're welcome here.

I'll be sharing projects, experiments, lessons, opinions, and the occasional rabbit hole.

Thanks for stopping by.

Now let's build something. 🚀

Comments


Comments are closed