[darkstar_16]

I don't think it's even a broad strategy from PM or higher ups. I actually think it's engineers inside the company who want to play with the coolest hardware and the build features for the newest stuff. Features can be made to work with older hardware but that requires more time and optimization which they never get, so someone takes a call that x and y features only work on newer gen hardware.

[bionsystem]

In my new position (on a different product) I don't have enough fingers to count how many times the previous guy bullshitted the PO/PM with "that's not possible" of having some features / workflows enabled. Just because he didn't bother thinking through it or just didn't want to do it. Most of the stuff is a bit boring but just a few days of work and test. So yeah I entirely agree with you.

[coldtea]

>I don't have enough fingers to count how many times the previous guy bullshitted the PO/PM with "that's not possible" of having some features / workflows enabled. Just because he didn't bother thinking through it or just didn't want to do it.

Or just because if somebody who knows the code inside out doesn't shoot down most new stupid feature requests, the product would end up a slow overcomplicated mess of random features and technical debt.