Engineers have far less control over that process than most people realize. Management, accounting, and the execs that signed off on it are to blame. Every time.
Oh I’m sure an engineer thought about that, reported it, but the effort involved in a new “add to library but don’t automatically download regardless of user setting” did not fit Bono’s timeline
Yes, generally that’s true. And also many managers are engineers who moved into a role. I find it unlikely though in this case “add an album to every single Apple account” went through a proper engineering/spec audit and missed what is almost certainly the most blaring edge case
So either it was intentional, which is more likely in either scenario of “if we do this x will happen without us spending engineering time on preventing x so let’s just do it” or “we want x to happen, that’s the goal”.
The alternative is it never went through a proper audit/spec and was given as a direct task, either in an admin user interface or “run this db migration to add this album to everyone’s account” which is a failure in process or a deliberate circumvention of said process.
Best engineers you can hire with money did this. And people still believe neuroslop is good.
Engineers have far less control over that process than most people realize. Management, accounting, and the execs that signed off on it are to blame. Every time.
Oh I’m sure an engineer thought about that, reported it, but the effort involved in a new “add to library but don’t automatically download regardless of user setting” did not fit Bono’s timeline
Or, get this, even good engineers make big mistakes sometimes. We don’t get to blame managers for everything
Yes, generally that’s true. And also many managers are engineers who moved into a role. I find it unlikely though in this case “add an album to every single Apple account” went through a proper engineering/spec audit and missed what is almost certainly the most blaring edge case
So either it was intentional, which is more likely in either scenario of “if we do this x will happen without us spending engineering time on preventing x so let’s just do it” or “we want x to happen, that’s the goal”.
The alternative is it never went through a proper audit/spec and was given as a direct task, either in an admin user interface or “run this db migration to add this album to everyone’s account” which is a failure in process or a deliberate circumvention of said process.
Or they designed it to have plausible deniability that their back end was not spaghetti coded.
I don’t think there was any engineers involved even. It was just a change by the non-technical apple music administrators