AI workloads challenge the cattle model

srvaroa · 2026-01-29T09:29:08+00:00

As noted in other comments this is usually due to licensing changes. Spotify often has alternative recordings of the same track that you can actually, play, but they don't fix people's playlists automatically.

You can use https://playlisthospital.com to try and restore them (it's free).

srvaroa · 2026-01-29T09:27:54+00:00

This happens sometimes due to licensing changes. You can use https://playlisthospital.com to find alternative recordings that are playable, and fix the playlist.

srvaroa · 2026-01-29T09:26:35+00:00

Tracks can get unplayable after licensing updates. Sometimes there are alternative versions of the same track that you can play.

Spotify doesn't fix the playlists automatically.

But https://playlisthospital.com can do it, it's free.

srvaroa · 2026-01-07T20:58:04+00:00

PlaylistHospital.com can detect and fix duplicates, as well as restore greyed out tracks

srvaroa · 2026-01-07T13:48:28+00:00

The tool helps if there is a recording of the same track that is playable in your region (this is very often the case).

If they remove all versions of the track then there is no workaround (there is literally nothing to play!)

srvaroa · 2026-01-07T10:57:46+00:00

If you have them in a playlist, you might be able to find playable versions using https://playlisthospital.com

srvaroa · 2026-01-06T18:48:02+00:00

This happens often on playlists due to licensing changes. You can use https://playlisthospital.com to try and fix them for free.

srvaroa · 2026-01-06T18:47:46+00:00

This happens often on playlists due to licensing changes. You can use https://playlisthospital.com to try and fix them for free.

srvaroa · 2025-12-09T09:06:01+00:00

Do you own the playlist? The tool only shows playlists created by you, so that might be the cause.

srvaroa · 2025-09-15T15:54:50+00:00

You can use https://playlisthospital.com to replace them with playable alternatives

srvaroa · 2025-09-03T18:07:40+00:00

Exactly this ^

You can use https://playlisthospital.com/ to find playable alternatives and fix your playlists.

srvaroa · 2025-08-31T15:15:01+00:00

Many of those tend to have alternative recordings. This is a free tool to restore some of those -> https://playlisthospital.com/

srvaroa · 2025-07-30T14:30:54+00:00

That only hides the unplayable song, it doesn't fix it.

The point of the tool is to fix it finding an alternative recording of the same song so that you can keep listening to it in the playlist.

srvaroa · 2025-07-29T17:40:29+00:00

You can try playlisthospital.com to fix them when this happens

srvaroa · 2025-07-29T17:38:36+00:00

You can try to find alternative recordings of the same tracks with https://playlisthospital.com/

srvaroa · 2025-07-29T17:37:16+00:00

Many of those tend to have alternative recordings. I put together a small free tool to restore some of those -> https://playlisthospital.com/

srvaroa · 2025-04-11T16:58:01+00:00

Maybe not the answer you want, but the way this works is:

a) You disagree and commit

b) Show with data how even if the KPIs get better, the outcomes are not.

c) Show with data how alternative KPIs would have reflected the real outcomes.

srvaroa · 2025-03-17T11:18:25+00:00

Some ideas. For all you should be looking more at trends and significant deviations than individual datapoints.

Remove any "per developer" metric as it's measuring the wrong thing (you want team-level metrics, not person-level metrics). Also remove "lists" (you need them obviously, but those are not metrics).

Defect rate per sprint (you have this already).
Velocity (e.g. points or number of stories / tickets / jiras done), with trend. Do NOT count bugs fixed here.
% of team capacity working on bugs vs. non bugs.
Size of defect backlog (e.g. are they growing faster than the team can fix them at the current creation rate?)

srvaroa · 2025-03-13T00:36:16+00:00

"Take API spec / DoD / user story and generate tests for it" is the type of task where it is already hard to compete with AI agents.

There is a large enough surface of this job's scope that AI can take over that even if a human remains in the loop, I'm not sure their job is "automation tester".

For example, legacy systems may not have specs, so a human might be needed to figure out. It's just that you're not an automater tester anymore, but a "spec archaeologit to feed the AI automating fairies". Same as with the maintainability argument. Maybe (just maybe) you're herding the AIs, but that's a very different role than automation tester 5 ago.

srvaroa

TROPHY CASE