What happens when a senior engineer spots what 500+ tests and a green pipeline completely missed—not a missing line, but a missing abstraction? Here's why that judgment cannot be delegated to an AI, and why patching your prompts won't save you.

What happens when you pick a domain where sloppy thinking has real consequences? A production-grade cashback platform backend—live, continuously deployed, and engineered around the constraints that make financial systems genuinely interesting.

What happens when a senior engineer opens your GitHub repo instead of just reading the README? A tour of the decisions, constraints, and practices worth examining in the ClickNBack codebase—including how AI fits into a disciplined engineering workflow.

What happens when the project you've been building turns out to be the wrong proving ground? After two months away, here's the honest story of why everything changed—and why that clarity was worth waiting for.

What happens when your runner needs to build Docker images and you hit resource ceilings? This post covers the Docker socket challenge, practical resource management, and the deeper engineering lessons learned from running CI/CD in your own lab.

What happens when manual setup becomes operational toil? This post dives into the pain points of token expiration, the journey to automation with Personal Access Tokens, and how Docker restart policies and config volumes make runners truly hands-off.

What happens when cloud CI/CD costs meet home lab reality? This post explores the motivation for self-hosted runners, the decision process around runner scope, and why Docker is the natural choice for isolation and manageability.

What happens when you realize that writing too much documentation too soon might be your biggest waste of effort? Can vertical slices and living documents save you from over-planning? Here's why I'm choosing one feature at a time, and how the lessons from functional requirements shaped my approach to API design.

What happens when you commit to building a full deployment pipeline in just seven days? Can you set up a Docker registry, CI/CD runner, and Kubernetes cluster without drowning in complexity? Here's my plan for turning three old ThinkCentres into a working production environment—and the discipline required to stay focused on what matters.

What happens when you decide to build infrastructure before writing a single line of business logic? Can prioritizing deployment over development actually make you a better engineer? Here's why I'm setting up my home lab cluster first—and what it says about thinking like a product engineer, not just a coder.