Spotify: Our best developers haven't written a single line of code since Dec
1–10 of 25 posts
Re: Spotify: Our best developers haven't written a single line of code since Dec
#2Interesting, I will have to test that. Does Spotify have any security bug bounties? :D
Re: Spotify: Our best developers haven't written a single line of code since Dec
#3"They actually only generate code and supervise it."
I wonder what "supervise" means...
Re: Spotify: Our best developers haven't written a single line of code since Dec
#4Interesting, I will have to test that. Does Spotify have any security bug bounties? :D
Anna's Archive recently tested that successfully.
Re: Spotify: Our best developers haven't written a single line of code since Dec
#5The really interesting part is what this system runs on.
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...
Re: Spotify: Our best developers haven't written a single line of code since Dec
#6Spotify hasn't released a new useful feature or improved any existing one since ~2018, IIRC.
They did however, remove many useful ones.
Re: Spotify: Our best developers haven't written a single line of code since Dec
#7"They actually only generate code and supervise it." I wonder what "supervise" means...
It means code review, except now you're reviewing code you didn't write, for a system you didn't design, generated by a model that can't explain its reasoning. That's a harder job than writing it yourself, not an easier one.
Re: Spotify: Our best developers haven't written a single line of code since Dec
#8The really interesting part is what this system runs on. 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 thi…
> 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.
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 ;-)
Re: Spotify: Our best developers haven't written a single line of code since Dec
#9The really interesting part is what this system runs on. 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 thi…
> a framework for applying code changes across hundreds or thousands of repositories at once
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?
Re: Spotify: Our best developers haven't written a single line of code since Dec
#10They’re probably spending all their time on Teams calls like everyone else.