A correct JWT verifier does eight things. Most production verifiers I have read do four or five of them. The other three or four get skipped because the library defaults aren't loud about them, the docs gloss over them, or someone copied a "it works" snippet from Stack Overflow circa 2018. Here is the full eight-check list, what each one prevents, and what it looks like to implement them with stru
The Problem Most engineers deploy to Kubernetes by clicking buttons in a UI. I built Archnet — a fully automated Internal Developer Platform What is an Internal Developer Platform? An IDP is the infrastructure layer that sits between your code How code gets deployed How secrets are managed How the system monitors itself How failures get detected and fixed Most companies pay Humanitec or Backsta
We had ArgoCD running perfectly. Every deployment was reconciled from Git. Drift detection worked. Rollbacks were one-click. Our GitOps setup was clean. Developers still couldn't provision a staging environment without pinging the platform team. That gap — between "GitOps in place" and "developers can actually self-serve" — is where most platform engineering teams get stuck. GitOps solves a real p