Live data from Hacker News

Spotify: Our best developers haven't written a single line of code since Dec

seekingalpha.com

21–25 of 25 posts

Re: Spotify: Our best developers haven't written a single line of code since Dec

#21
post #5

The 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?

Imagine you initialized 10,000 NPM repos identically simultaneously. Then had 100 different teams each take of 100 those repos for 10 different projects, and let each repo run for 1,000 commits. How distinct would each of those repos be? How might have they evolved independently? What types of interesting patterns might be adopted to improve development experience, or detect bugs by each team? What packages at what version might be most popular?

Now imagine you had the tools to do a diff across all those repos simultaneously, and classify, group, and review those patterns. What could you learn NPM teams and practices?

Now imagine you could pick best of breed, and propagate those back to all the other projects automatically to improve their productivity, security, etc. How fast would your productivity improve and your engineering culture change if everyone could automatically learn the best of what everyone else had to offer?

Companies like Spotify have sophisticated tooling for detecting repo changes and enforcing policy like that, and they run that experiment 1,000 times a day. Small evolutions in what was an identical build script, like a version bump, are detected, and if it passes a threshold it can be rolled out everywhere else immediately.

Having all the copies that you can sync up centrally periodically puts natural selection to work on internal best practices.

Basically, things work differently at scale. When the number developers you employ approaches a meaningful percentage of the total number of developers globally, your internal diversity starts to mirror the global diversity. So you have to manage that diversity. If you freeze policy entirely, you fall behind the global average. If you let things run wild, your company fractures technologically.

So, make a 1,000 copies, see what pops up, adopt and enforce things that look good, then do it again. Evolve to the next best place you can be from where you are.

Re: Spotify: Our best developers haven't written a single line of code since Dec

#22

Earlier quoted context omitted.

It is unusable you cannot go to your music library without being exposed to advertisements.

you know you can pay them money, right?

how does one get used to the taste of leather, rubber, dirt and gravel? is there much nutrition there?

Re: Spotify: Our best developers haven't written a single line of code since Dec

#23

Earlier quoted context omitted.

> 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?

Imagine you initialized 10,000 NPM repos identically simultaneously. Then had 100 different teams each take of 100 those repos for 10 different projects, and let each repo run for 1,000 commits. How distinct would each of those repos be? How might have they evolved independently? What types of interesting patterns might be adopted to improve development experience, or detect bugs by each team? What packages at what v…

This sounds totally retarded.

Why would spotify have 10000 npm repos?

Re: Spotify: Our best developers haven't written a single line of code since Dec

#24
post #12

I wonder how it works and how much heavy lifting "supervising" is doing. Whenever I try to use AI, the outcome is about the same. It's good at non-critical things like logging or brute force debugging where I can roll back after I figure out what's going on. If it's something I know well, I can coax a reasonable solution out of it. If it's something I don't know, it's easy to get it hallucinating. It really goes off…

There's no definitive way to tell if some code is written by AI or not; thus their statement doesn't have to be true. Usage of AI itself is nebulous, it could mean anything from OpenClaw-style automated agents to someone prompting an LLM via chat to an engineer manually writing code after wasting hours trying to get an agent to do it (that still counts as "usage", even if not ultimately productive). The market curren…

Existing large market products and services most likely will not bring down the price of their goods and services even if AI reduces the cost to produce.

There is a saying in sales, "Money left on the table". People are already willing to pay current market value prices so they will keep doing so. Why decrease your profits when people are already willing to pay? Keeping the same pricing would maximize profits and stock, a bonus.

New companies that start producing alternative solutions would most likely be the ones to utilize the reduction in cost for producing with AI. It would be their way to get a foot in the door and start building market.

Organizations that focus on providing a good or services to the vulnerable would be an exception. Some companies that market on cost would be in that mix too.

Re: Spotify: Our best developers haven't written a single line of code since Dec

#25

Earlier quoted context omitted.

There's no definitive way to tell if some code is written by AI or not; thus their statement doesn't have to be true. Usage of AI itself is nebulous, it could mean anything from OpenClaw-style automated agents to someone prompting an LLM via chat to an engineer manually writing code after wasting hours trying to get an agent to do it (that still counts as "usage", even if not ultimately productive). The market curren…

Existing large market products and services most likely will not bring down the price of their goods and services even if AI reduces the cost to produce. There is a saying in sales, "Money left on the table". People are already willing to pay current market value prices so they will keep doing so. Why decrease your profits when people are already willing to pay? Keeping the same pricing would maximize profits and sto…

Fair, but in this case you'd still expect LLMs to be a massive boon to startups wanting to compete with the established players?

I'm not seeing any of that happening either, which I'd expect if the AI productivity claims were true and anyone could just vibe-code an entire sustainable business.

Post reply on HN