swol@kpujji:~/blog/hello-world$
~/blog/hello-world.md

hello, world

Why this blog exists, what I'll write about, and how it's built.

1 min read

Every solutions engineer has a folder of half-written notes: the architecture sketch from a customer call, the workaround that saved a rollout, the thing you explained for the fifth time that month. This blog is where those notes go to become something finished.

What I’ll write about

I work in post-sales solutions engineering. My job starts after the contract is signed, when the real question becomes “is this actually helping?” That vantage point shapes most of what you’ll find here:

  • Application observability: instrumentation, tracing, error monitoring, and the gap between collecting telemetry and using it.
  • AI data governance: what responsible AI looks like in real data pipelines, written while I work toward the IAPP AIGP.
  • Humans in the loop: designing AI workflows where a person stays informed, empowered, and accountable.
  • 3D printing for real problems: small, practical fixes, with the CAD and the failures included.
  • Automation and personal systems: smart home, scripts, and tools that take load off my brain.
  • Sustainable careers: burnout, focus, and staying good at a demanding job without it consuming you.

How it’s built

Posts are Markdown files in a Git repo. Astro turns them into a static site, and Cloudflare serves it from the edge. There’s no client-side framework and no tracking script, just HTML, CSS, and a little JavaScript for the theme toggle and copy buttons.

The terminal aesthetic is on purpose. Most of my best thinking happens somewhere between a shell prompt and a whiteboard.

$ git commit -m "hello, world"

If something here helps you, or you think I got it wrong, I’d like to hear about it.