Guardrails Matter More With AI Than Infrastructure

Because mistakes scale faster. Infrastructure mistakes scale with traffic. AI mistakes scale with usage and trust. That is faster. AI Errors Feel Plausible AI failures are dangerous because they often look reasonable. The output is coherent. The tone is confident. The result is wrong. That combination spreads errors quietly. When infrastructure fails, it fails loudly. Services return 500 errors. Dashboards turn red. Alerts fire. The failure is obvious and immediate. ...

December 20, 2025 · 4 min · Jose Rodriguez

We Use AI to Enforce Patterns, Not Generate Solutions

Guardrails over guesses. We are deliberate about how we use AI. We do not ask it to invent solutions. We ask it to follow patterns. Patterns Encode Experience Patterns exist because something worked. They represent lessons learned, mistakes avoided, and decisions made. AI is very good at following rules. It is less good at choosing them. Patterns are distilled experience. A retry pattern with exponential backoff exists because someone learned the hard way that constant retries overwhelm systems. A specific logging format exists because it makes debugging easier. A particular testing structure exists because it catches common mistakes. ...

December 17, 2025 · 3 min · Jose Rodriguez

Role Assignment Sprawl in Azure and How It Starts

Role assignments multiply faster than you expect. Here is how we went from structured permissions to chaos, and how we fixed it. It Starts With One Exception You build a clean RBAC model. Groups for teams. Roles at the right scope. Least privilege enforced. Then someone needs access for a demo. Just this once. You add a direct role assignment to their account. You plan to remove it later. You forget. ...

November 5, 2025 · 4 min · Jose Rodriguez

Why We Stopped Letting Teams Build Their Own Pipelines

Consistency beats flexibility at scale. Early on, we let teams build their own pipelines. It felt empowering. It felt flexible. It felt fast. It did not scale. Flexibility Creates Variance When every team builds pipelines independently: conventions diverge checks differ deployments behave differently failure modes multiply That variance is invisible at first. It becomes painful later. Team A used Azure Pipelines. Team B used GitHub Actions. Team C used Jenkins because they inherited a project that already had it. All three were valid choices. ...

June 20, 2025 · 3 min · Jose Rodriguez