A look at how maaldo.com evolved over 20+ years—from a simple LAMP stack to a modern cloud-native platform for experimentation, automation, observability, and continuous learning.
I’ve owned maaldo.com for more than 20 years. It has served as both my personal website and my technical sandbox for as long as I’ve been building on the web. The name itself comes from the first two letters of my first, middle, and last names: (Ma)tt (Al)len (Do)ering.
What started as a simple personal site eventually became something much more meaningful. Over time, maaldo.com has evolved alongside the web itself - from a basic LAMP stack to classic ASP, .NET WebForms, MVC, WCF, REST APIs, MongoDB, and responsive design. Each version reflected not only changes in technology, but also changes in how I think about software architecture, maintainability, and engineering discipline.
More than just a website, it has always been a place where I could learn by doing. It gave me room to explore technologies beyond my day-to-day responsibilities, modernize older implementations, and apply real engineering practices to a system I fully owned end to end. That has made it one of the most valuable long-term learning platforms I’ve had.
Over the years, the site has consistently been a place to:
The latest iteration of maaldo.com reflects the kind of architecture I enjoy building most: modern, observable, automated, and designed with room to evolve.
Today, the platform includes:
The goal is not just to use modern tools for their own sake, but to build the site in a way that mirrors production-style thinking: clear separation of concerns, automation wherever it adds value, strong observability, and an architecture that can adapt as requirements change.
The full implementation is available publicly and reflects the same principles behind the site itself: production-style structure, containerized deployment, CI/CD automation, and an observability-first design.
More than two decades later, maaldo.com is still evolving. It remains a living system - part portfolio, part laboratory, and part long-term engineering journal. As new technologies emerge and my own thinking continues to mature, the architecture continues to change with it.
In many ways, the story of the site is also the story of my growth as an engineer: learning, rebuilding, simplifying, modernizing, and always looking for a better way to design and deliver software.
