Why platform teams fail (and AI makes it worse)
Groady
18 points
6 comments
November 14, 2026
Related Discussions
Found 5 related stories in 171.2ms across 12,728 title embeddings via pgvector HNSW
- The AI Situation in Software Development srikanthdotch · 41 pts · August 15, 2026 · 62% similar
- Why don't more developers "use the platform"? vinhnx · 49 pts · October 04, 2026 · 61% similar
- The growing divide between AI hype and software engineering reality jruohonen · 60 pts · August 29, 2026 · 61% similar
- Experience Necessary. The Irony of Building a Skilled Team in the Age of AI another-dave · 15 pts · September 15, 2026 · 60% similar
- AI handles incidents, engineers lose touch with their systems sylvainkalache · 372 pts · September 05, 2026 · 60% similar
Discussion Highlights (3 comments)
d3p0
The point about agents finding tools through AGENTS.md and skills rather than a portal matches my week. We added an AGENTS.md to every repo and rewrote our setup tutorial as a skill an agent can follow, and that took an afternoon. The guardrail half was harder, and it failed in a way the article doesn't cover: silently. We require every commit in a PR to be signed. It was written down and enforced by a required check. A contributor's PR still sat for six days, because on a fork the check waited for a maintainer to approve the run and told the author nothing. Nobody was blocked by policy; they were blocked by a guardrail that didn't speak. We changed the check to comment on the PR with the exact commits, the reason and the two commands that fix it. A guardrail that fails without telling anyone is as bad as a golden path nobody can find.
bad_username
The article highlights the key aspect which is often forgotten or neglected: the challenge of a large enterprise transformation project (like platform development and adoption) is no more technical than it is political and organizational. The greatest technical vision will fail if there is no efficient decision making structure, political kinetic energy, or process authority around it.
lowbloodsugar
The problem is simple: everyone underestimates the size of the operations/maintenance effort required. The team was simply too small. The team is too small because no-one wants to pay for it. Every team that uses it has their own budget to do their own things. Because these teams do application development instead of platform development, they underestimate and undervalue the work involved. They are literally not competent when it comes to evaluating the cost of the platform.