Tag: platform-engineering
All the articles with the tag "platform-engineering".
The Code Changed. The Description Had to Survive It.
Code changes flow back into the knowledge graph the generator reads: changed files only, merge not replace, both artifacts patched. Freshness as write back, not retrieval ranking.
I Could See Every Resource. I Still Could Not Rebuild It.
Taking over cloud infrastructure someone else built, and why a read-only inventory answers the easy question rather than the one that decides the handover.
Nobody Typed the 10,000 Lines. The Review Belonged Upstream.
In a generated system the unit of review is not the output, it is the template that emitted it, because a defect there ships in every instance at once.
The Model Wrote the Code. The Build Gate Was the Product.
An AI code generator that must compile and run its own output before it delivers, and the exit conditions that keep the loop from hanging.
One Shared Service Account Would Have Been 200 Lines Shorter
A generated graph of 131 services can share one identity or carry 131 of them. The second costs 216 IAM bindings, and it is the only version where a leaked credential is survivable.
Every Deploy Reported Success. The Endpoint Had Been Unreachable for Two Weeks.
A 404 is not one thing, and the difference between text/plain, text/html and application/json was the entire diagnosis.
Two Environments, One Resource. The Label Said 'dev'. The Name Said Otherwise.
Adding multi-environment support to a platform that names its resources by service, and the collision that every successful deploy silently confirmed.
Delete the State File. Redeploy. Nothing Should Happen.
How generated Terraform learns to adopt infrastructure it did not create, and the three ways a cloud inventory lies about what things are called.