I’ve been telling this to developers for years. The real way to do it is have the delay increase over time matching their release schedule. So if you do quarterly releases have the system incrementally show down over three months until it’s 20% slower than it was. Then reset the delay when you put out the new version. People will think every version is faster than the last.
no its not. Planned obsolescence is planning for something to HAVE to be replaced. This isnt it being replaced, its faking fixing a problem with the code of the same product and because you dont need a new license for product you dont have to replace it you just update it which is legally distinct.
Huh