fl@latini.dev:~/posts$ ls -t --human --sort=time
posts=36 total_read=~397 min range=2022-2026
# Your Paved Road Starts at git push
Most internal platforms pave everything after the push and leave everything before it to a README. Why the inner loop (clone, run, change, see it work) is the part of the developer's day the platform never touches, why a three-day local setup is a platform defect rather than a rite of passage, and how to pave it: one command from the template, an explicit decision per dependency, local credentials by identity, seed data that exists, and honest measures of clone-to-running.
# Your Build Is Slow Because Everyone Owns It
CI pipelines get slow and flaky without anyone deciding they should, because every team owns a step and nobody owns the total. Why feedback-loop latency is a platform capability rather than a per-repo chore, the arithmetic of engineers waiting, why flaky tests are a trust problem and not a test problem, and how to run the build as a product: a time budget, caching as a primitive, runners sized on queue time, quarantine with an owner and an expiry, and honest measures of push-to-signal.
# Your Platform Stops at the Database
Most paved roads cover the stateless half of a service and hand the data to a ticket queue. Why platform teams stop at the database, why "we use a managed service" is not a data platform, why a backup nobody has restored is a hypothesis, and how to pave the data road: provisioning from the template, identity-based access, schema migrations as deploys, restores as a drilled self-service command, and a clear line between what the platform owns and what the team owns.
# Nobody Merges the Dependency Bot's Pull Requests
Every team turned on the dependency bot, and every team has a hundred unmerged update PRs. Why staying current fails when it is shipped as a notification to each repository, why drift compounds until it becomes a forced migration, and how a platform team turns currency into a fleet property: platform layers upgraded once, grouped updates that merge themselves on evidence, majors run as campaigns, and lag measured instead of PRs counted.
# The Estate You Cannot Enumerate
Most organisations cannot answer "what is running, on what, and who owns it" without starting a project. Why the inventory gets rebuilt in a panic for every CVE, migration, audit and cost sprint, why a service catalogue is a declaration rather than an observation, how ownership decays at the speed of reorgs, and how a platform team turns the inventory into a standing capability that answers in one query.
# Your Platform Team Is Hiring for Year One
Most platform teams hire against an infrastructure job description long after the job stopped being infrastructure. Why the interview loop selects for builders when year two needs product, support, teaching and programme instincts, how to rewrite the job description from the team's actual calendar, what to test for instead, and why the career ladder quietly undoes all of it.
# You Build It, You Run It. With What?
Most organisations hand stream-aligned teams the pager and call it ownership, then watch every hard incident drift back to the platform team because they are the ones who understand the substrate. Why operational ownership has to ship as a paved road rather than a slogan, how to split runbooks into the part the platform generates and the part the team owns, and how to help on the first incident without becoming the escalation path for the whole estate.
# The Migration With a Date on It
A runtime end of life, a datacentre exit, a cloud service retirement: the migration you did not choose, with a deadline you cannot move. Why these fail as governance rather than as engineering, how to find the real internal date, why the inventory is the critical path, and how a platform team turns sixty bespoke migrations into one migration applied sixty times.
# Who Pages the Platform Team?
Platform teams sell on-call, SLOs and incident practice to everyone else, then run their own service on hope and Slack. Platform incidents have a different shape: they block change rather than take things down, they fan out across every team at once, and the users have a workaround that costs you more than the outage. How to page on the road rather than the components, what a platform SLO can honestly measure, and how to staff a rota with six people.
# The Platform Team's Second Year
Year one of a platform team is a build. Year two is a run, and almost nobody re-plans for it. The maintenance ratio nobody budgets, why success is what generates the load, how to put the run cost in the plan in public, and the year-two failure mode nobody names: inventing a project to prove the team is still needed.