Jero Sanchez

A Story of Infinite Refactor

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:
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 ⟶

The Rest Of The Story:

Catch up on the chapters that brought me here.

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 ⟶

Living Documentation: Why I'm Not Writing API Contracts Yet

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.
Read more ⟶

Building the Pipeline: From Registry to Production in One Week

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.
Read more ⟶