Jero Sanchez
Backend engineer. Building things that last.
Welcome back!Here you have the latest
chapter of my story, ready for the curious mind. Grab a seat, get comfortable, and let’s see
what new twists are on the table today:
Before You Ask: What You'll Find If You Read ClickNBack
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.
Read more ⟶The Rest Of The Story:
Catch up on the chapters that brought me here.
The Pivot: Why I Dropped a Marketplace for a Cashback System
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.
Read more ⟶CI/CD in the Home Lab: Docker Gotchas, Resource Limits, and Real Engineering Lessons
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.
Read more ⟶Operationalizing GitHub Runners: Tokens, Automation, and Persistence
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.
Read more ⟶Thinking Through a Self-Hosted Runner: Why, Scope, and Dockerization
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.
Read more ⟶