Back to Blog

Hello, World!

·

1 min read

· Meta

The beginning of something new — rebuilding my personal site with Go.

👋 Welcome to the new version of my site — now built entirely1 with Go.

I finally took the plunge and rebuilt everything from scratch. After years of using a #php site that I never fully finished, I scraped the old and started fresh. This ditched #laravel in favor of a bespoke #go stack I created for my projects — mallardduck/go-web.

The stack2:

Go
Server-side rendering via the templ templating engine. Compiled to a single binary — no runtime to install, no interpreter to babysit.
Tailwind CSS
Utility-first styling. The output CSS is purged at build time, so production pages stay lean.
YAML & Markdown
Content and config live in flat files — no database needed for what this site does today.
Markdown
Blog posts (like this one!) parsed with Goldmark and rendered to HTML at startup.

# Why Go?

I’ve been writing #go professionally for a while now, working on #k8s tooling and observability infrastructure at Rancher by SUSE. It felt natural to bring that expertise here.

In the past, I preferred #PHP for the same reasons. It was what I knew from work and I wanted more excuses to keep using it. Doing the same with #go lang feels like a natural fit now too.

Go’s simplicity, performance, and excellent standard library make it a joy to work with. And deploying a single static binary with zero runtime dependencies is… honestly still a little magical every time.

# What’s Next?

I’ll be writing here about topics I work with every day:

  • #kubernetes and container orchestration
  • #Go programming tips and patterns
  • #linux system administration
  • Open source projects I’m contributing to

There will also be occasional trips down memory lane, going over previous jobs and projects.

Stay tuned! 🚀


  1. I said entirely, but technically speaking Node.js is involved still. It’s necessary for compiling static assets and rendering graphs. ↩︎

  2. The new one, not the old one. ↩︎