21–30 of 72 posts
My employer is considering using backstage for our data infrastructure tooling. This makes me nervous because Spotify seems unable to program a reliable shuffle feature on their player. Maybe it's because they put all the good devs on backstage?
My employer is considering using backstage for our data infrastructure tooling. This makes me nervous because Spotify seems unable to program a reliable shuffle feature on their player. Maybe it's because they put all the good devs on backstage?
Spotify's shuffle algorithm can't be changed easily because too many people rely on its existing quirks. Which means that Spotify's ability to keep it at a reliably stable level of unreliability for so long, through so many other platform changes, makes it a prime example of why Spotify is a perfect choice for enterprise! ;)
Has anyone successfully implemented Backstage at their company? How'd it go? We're looking at it for an internal platform serving ~50 engineers today, spanning mobile, backend, enterprise integrations, and ML teams. The hope is it'll make it easier to spin up new things "the right way" without e.g. ML PhDs having to learn Helm and K8s, plus other goodies like nice docs.
I’ve always thought Backstage seemed like an interesting solution to existing god awful “solutions” many enterprise type companies subject their devs to. For example, PostHog, Swagger.
I’ve always thought Backstage seemed like an interesting solution to existing god awful “solutions” many enterprise type companies subject their devs to. For example, PostHog, Swagger.
I’ve always thought Backstage seemed like an interesting solution to existing god awful “solutions” many enterprise type companies subject their devs to. For example, PostHog, Swagger.
[flagged]
What do you mean by "sensible"? Spotify has playlists, but most listeners simply don't bother. Plus, it's obviously convenient for the platform to actually control what you're going to listen to next, so obviously they'd rather emphasize the "magic" auto-queueing (which, tbh, kinda works well-enough).
Spotify's queue doesn't do that, at least on windows. Instead, playing the first album adds it to a queue but not the queue. Selecting more albums inserts them after the current track, not after the album. If I decide I want to remove the remaining tracks of the first album from the ghost queue and only listen to the queue I have to remove them one by one. And the most bonkers part, is when removing the last remaining track from the first album's ghost queue, Spotify replaces it with a different track from the first album! There's no way to remove the ghost queue.
The workaround is to simply not use the play button and only add albums to the queue by clicking into the ellipsis menu, but it's a bit of a kludge and not what I'd call sensible. Plus for some reason I always go for the green play button first, then decide later that I want to add a few more albums to the queue
The problem you end up having is that (for example) Google docs is really good for writing and commenting on docs, and a general purpose tool is never going to be as good as Google docs for docs. You could write a "Google Docs" plugin and just link out to a project's google doc but then you're just a link aggregator which offers limited usefulness.
Has anyone successfully implemented Backstage at their company? How'd it go? We're looking at it for an internal platform serving ~50 engineers today, spanning mobile, backend, enterprise integrations, and ML teams. The hope is it'll make it easier to spin up new things "the right way" without e.g. ML PhDs having to learn Helm and K8s, plus other goodies like nice docs.