Your Cluster Is Already Watching. That's the Observer Pattern. At some point, most platform teams hit the same wall. A service goes down. An secret expires. A node runs out of disk. And the first question in the postmortem is always the same: why did...
The Facade Is the Product There's a question that comes up in almost every platform team at some point: Should we expose Kubernetes directly to developers, or should we abstract it? It sounds like a tooling debate. Backstage vs. raw manifests. Helm c...
Your Platform Provisions Environments. That's a Factory. Every platform team eventually faces the same request, over and over again. A developer needs a new environment — staging, a feature branch, a sandbox for testing. They open a ticket, fill out ...
Design Patterns Are Not a Developer Thing At some point, most platform engineers end up in a conversation with a senior dev or a software architect where you're trying to explain how your infrastructure works. And somewhere in the middle of that conv...
El setup típico que veo: bash ml-project/ ├── .git/ ├── src/ │ └── train.py ├── data/ │ └── training.csv # 5GB, in Git └── models/ └── model.pkl # 2GB, in Git Primera pregunta: ¿Cómo está esto en Git? Respuesta común: bash # .gitignore ...
Terraform, Helm, GitOps... ¿para entrenar modelos? Sí. Hoy: Cómo gestionar todo eso como código. El problema: Tienes tu stack de Platform Engineering: Terraform para infraestructura Helm para aplicaciones en K8s ArgoCD para GitOps CI/CD pipeline...
