Open to Work: Senior Backend & Distributed Systems Engineer (Go / Python) View LinkedIn →

The Backend Engineer's Playbook

Technical Journal // The Backend Engineer's Playbook
Mar '26

AI Coding in 2026: Productivity Multipliers vs. Skill Replacements

Two years of coding with AI every day: what actually saves time, what creates hidden debt, and why your fundamentals are your only real defense against hallucinated correctness.

Feb '26

Fast Docker CI: Stop Rebuilding Container Images on Every Commit

Rebuilding multi-stage Docker images on every code change wastes minutes and cache. How to decouple build dependencies from runtime containers for instant feedback.

Feb '26

Python Background Workers: Architecture, Queues, and Retry Strategies

Learn how to build production-ready Python background workers that scale under load. Covers worker pools, queue architecture, retry strategies, idempotency, and graceful shutdown.

Jan '26

Go Struct Field Alignment: How Memory Padding Wastes Your RAM

How CPU word alignment and struct field ordering silently inject memory padding in Go. Learn field reordering to cut heap memory allocations and cache misses.

Jan '26

Memory Mechanics In Go - Stack vs Heap

When thinking about performance, it's easy to focus on Big O notation. But in Go, the difference between the Stack and the Heap is often the difference between a service that scales and one that chokes on GC pauses. This post explores escape analysis, the "Pointer Myth", and why passing by value is often 40x faster than passing by pointer.

Jan '26

OLTP vs OLAP - Why You Need Two Databases

"The database that runs your app cannot be the database that analyzes your app". It's a hard lesson learned at scale. Early on, Postgres does it all. But as you hit massive scale, your analytics queries start killing your login APIs. This post breaks down the physics of Row-oriented (Couchbase) vs Column-oriented (ClickHouse) databases, and how to bridge them using Change Data Capture (CDC) for a robust, lag-free architecture.

Jan '26

Go Garbage Collector Mechanics: Pacer, GOGC, and Allocation Latency

How Go's concurrent tri-color mark-sweep collector works under the hood. Learn pacer triggers, GOGC tuning, and zero-allocation memory pool patterns.

Nov '25

What Couchbase Taught Me About System Thinking

Working with Couchbase for the past year and a half has been more than just learning a database. It has been an exercise in system thinking: seeing how indexes, queries, consistency, and durability interact, and how small design choices ripple through performance and reliability. This essay is my personal notebook from that journey. It is technically dense because Couchbase demands precision, but it is also reflective because the lessons extend beyond one database. Understanding how array indexes multiply entries, why compound index order matters, or how query consistency flags change latency is not just about Couchbase, it is about learning to think in terms of systems, trade‑offs, and consequences.