Hey there! I’m Muhammad Huzair — a backend engineer who’s been in the trenches of production systems, chasing bugs at 3 AM, and rebuilding things that “shouldn’t have broken in the first place.”

This blog is where I document the real stuff: the production incidents, the subtle concurrency bugs, the database pitfalls, and the architectural decisions that look obvious in hindsight. No hand-wavy theory — just real problems I’ve hit and the solutions that actually worked.

Who Am I?

I build backend systems in Go, primarily focused on distributed systems, microservices, and high-throughput APIs. I’ve worked on order management platforms, fleet tracking systems, AI streaming backends, and billing services — all in production, all with real users, all with real bugs.

You can find more about my work and projects on my portfolio →.

The portfolio covers the projects I’ve shipped, the tech stack I work with, and a deeper look at the kinds of systems I love building.

What You’ll Find Here

Every post on this blog comes from something I actually ran into:

  • Distributed systems pitfalls — sagas, outbox patterns, event ordering problems
  • Go concurrency bugs — goroutine leaks, race conditions, channel deadlocks
  • Database performance — N+1 queries, connection pool misconfiguration, slow migrations
  • Resilience patterns — circuit breakers, retry strategies, rate limiting under load
  • Observability — how I debug systems I can’t directly inspect

These are the bugs that kept me up at night. Hopefully they save you some sleep.

Start Reading

Check out the latest posts below, or jump straight to a topic that matches the pain you’re feeling right now. If something resonates, feel free to reach out — I’m always happy to talk backend.

Happy debugging. 🐛