Spotify built Fleet Management back in 2022 to apply changes across thousands of repos. Half their PRs were already flowing through it before any AI was involved, but only for mechanical stuff like dep bumps and config updates. Claude Code is what let it understand what the code means, not just its structure.
The thing nobody's talking about is that none of this AI automation works without Backstage doing the boring work of tracking who owns what, how things build, and what depends on what.
I went through the Anthropic case study, Spotify's engineering blog series, and the full earnings call transcript here https://www.everydev.ai/p/blog-spotify-built-an-ai-coding-ag...
Do you mean that Backstage has the metadata like what services call which other services, and AI needs that to make changes safely? Sounds helpful to both AI and human developers ;-)
Statements like this raise fair questions. Is there code duplication across 1,000s of repos, and why respond by increasing surface area further with bespoke tooling?
They did however, remove many useful ones.
msie•1h ago
Nextgrid•1h ago