They haven't written code in years seeing how their piece of shit desktop app uses more ram and cpu cycles to stream 192kbps music in a day than the entire NASA stack for all Apollo missions combined. They should ask Claude to rewrite it in a real programming language
I just read it as "we were stuck and nobody got something done at all" to "we at least got something deployed". Going from zero to something mathematically speaking a very large increase (like infinite?).
> like infinite?
It's undefined because it's asking, "what is the inverse of 0/x" and x/0 has infinite correct answers if x = 0 and no correct answer if x ≠ 0.
Look into spotifyd if you want some resource usage sanity.
I can picture the entire hierarchy telling whoever's next up the chain what they're demanding to hear.
I'd be scripting the consumption of lots of credits and sending the output to /dev/null to get a glowing performance review.
Doesn't say anything about what their worst developers have been doing...
And just wait for when they force their developers (that are not writing any line of code), to go back onsite because "remote is bad"...
Spotify also keeps bewaking every update, so I do not trust their opinions
Cool, this is great. The sooner these apps start collapsing from ill-written and unchecked code the better.
P.s. Im not a SWE for a living but I can see through this crap.
Explains why the app hasn’t noticeably improved yet.
Spotify please open a limited time test api for experimenters without 250k DAU. There are people that would love to build that dont yet have that user base.
The best developers are probably wading through slop filled code reviews.
Is that why the Linux version is still broken?
The co-CEO gives a terrible example. A developer is working while commuting? How clear is one's thinking skills during that time? How safe is that to deploy a production commit? Does Spotify test in prod?
No mention of any code review in their example.
and why do they need to commute at all?
That explains a lot....
Man, a friend of mine hasn't written code for years. He generally comes in at least fifteen minutes late, using the side door - that way the boss can't see him, - and, uh, after that he just sorta spaces out for about an hour. He just stares at his desk; but it looks like he's working. He does that for probably another hour after lunch, too. I'd say in a given week he probably only does about fifteen minutes of real, actual, work, and even that's just filling out TPS reports.
[dead]
[flagged]