About

I’m a software engineer who’s spent 10+ years building production systems, hiring developers, and debugging decisions that seemed smart at the time.

This blog isn’t for beginners working through tutorials. It’s for mid-level to senior developers who’ve already shipped code and want to understand the tradeoffs, failure modes, and judgment calls that separate “works in demo” from “works at scale.”

What You’ll Find Here

Production lessons, not theory. Every article comes from real systems I’ve built, teams I’ve worked with, or decisions I’ve had to make (and sometimes undo). If I haven’t debugged it at 2 AM, I don’t write about it.

Tradeoffs over best practices. There are no universal “best practices”—only choices with different consequences. I write about when patterns break, what assumptions fail, and why the “wrong” solution sometimes ships better than the “right” one.

Judgment, not knowledge. You can look up syntax. You can’t look up whether to normalize that database schema, split that monolith, or rebuild that legacy system. This blog is about the decisions AI can’t make for you.

What You Won’t Find

• Tutorials. There are a thousand “Getting Started with…” posts already. You don’t need another one.
• Buzzwords. No “leveraging synergies” or “disrupting paradigms.” Just plain technical English.
• Hype. Every framework claims to solve everything. I write about what actually breaks.
• SEO padding. If you’ve already read the AI summary, you know the high-level points. You’re here for the nuance.

Why This Exists

Most technical content is either beginner tutorials or thought leadership fluff. There’s not much in between—writing for developers who’ve shipped production systems and want to understand why some choices work and others fail.

AI can summarize every framework’s features. It can’t tell you which one will slow your team down in 18 months. That’s what this blog is for.

About Me

I’ve built systems in Rails, Node.js, Go, and whatever else seemed like a reasonable choice at the time. I’ve hired developers, mentored teams, made architecture decisions I stand by, and made plenty I’d do differently.

I’m based in Ontario, Canada. When I’m not writing or coding, I’m probably running outdoors or traveling with my family.

If you want opinionated technical writing grounded in production experience, you’re in the right place.

Contact: Find me on Twitter/X, Threads, or Instagram.

Support: If these articles save you time or help you make better decisions, buy me a coffee.