Look, I get it. When I tell others I'm using Google Sites for my personal website, I usually get that look. You know the one – a mixture of confusion and mild disappointment, like I just told them I still use Internet Explorer or code in COBOL.

Here's the thing: I've been around the block. I've architected SaaS platforms, wrestled with AWS and Google Cloud infrastructures, and built enough database systems to make any SQL server blush. I've spent countless hours maintaining firewalls, developing coding frameworks, and keeping production systems running smoothly. I would think I know my stuff.

So why on earth would someone with my background choose Google Sites, of all things, for their personal website?

The answer is beautifully simple: because sometimes, less really is more.

Think about it. When was the last time you updated your WordPress installation? Remember that sinking feeling when you hit the update button, wondering if this would be the time everything breaks? Or that moment when your carefully crafted plugin stack decides to play a game of digital Jenga?

For my personal site, durocher.in, I wanted something different. Something that wouldn't wake me up at 3 AM with server alerts. Something that wouldn't require me to maintain a database, monitor system resources, or worry about security patches. I wanted a place where I could post my random thoughts and test out simple JavaScript projects without the overhead of managing a full-blown web infrastructure.

It's like my bobber motorcycle – stripped down to the essentials. Sure, I can't tell you exactly how much gas is left in the tank, but that's part of the charm. It's the same reason I love my 1980 GMC Jimmy, even though by modern standards it's practically analog. There's beauty in simplicity, in having just what you need and nothing more.

Google Sites gives me exactly that. No database? Perfect – that's one less thing to maintain. No complex deployment pipeline? Fantastic – I can focus on content rather than infrastructure. And while it may not be a dedicated web hosting service, Google's servers ensure my simple pages load faster than a caffeinated developer typing "Hello World."

Yes, I know what you're thinking. "But what about scalability? What about custom functionality? What about automated posting systems?" Here's my controversial take: I don't need any of that. Not here. Not for this purpose.

I can still use my own domain name. I can still make basic visual customizations. And most importantly, I can still share my thoughts and test my small projects without getting bogged down in the complexity that often comes with "proper" web development.

Is Google Sites the right choice for a business website? Probably not. Would I recommend it for a complex web application? Absolutely not. But for my personal corner of the internet, where I share my thoughts and tinker with code? It's perfect.

The tech world often pushes us toward more complexity, more features, more everything. We're told we need containerization, microservices, and enough monitoring tools to fill a data center. And sometimes we do! But not every project needs to be an enterprise-grade solution.

Sometimes, the best tool is the simplest one. The one that just works, stays out of your way, and lets you focus on what matters. For me, that's Google Sites. If you're running a full WordPress installation with custom plugins and automated deployment pipelines, that's great too. Different tools for different goals.

At the end of the day, technology should serve our needs, not the other way around. I chose Google Sites because it aligns perfectly with what I want from my personal website: simplicity, reliability, and zero maintenance. No downtime, no updates, no headaches.

And if someday I need to migrate to a more robust platform? Sure, it'll take some manual work. But that's a problem for future me. Right now, I'm happy with my digital bobber – stripped down, reliable, and exactly what I need.

 < BACK