I have a sense of how these decisions look in the board room— just curious what they look/feel like on implementation given that people presumably don’t enjoy putting in effort to make a thing worse, obviously don’t dox yourself and get in trouble at work!
In the companies I’ve worked for, those kind of things just don’t happen. But again, my career has been in for software targeted at very specific markets and users and not general consumption for harvesting. Anyone knowing me would know this is me , but… one was a state health department processing communicable disease reports, one was a software maker for window and door manufacturers. The current and previous were built around making the job easier and faster for other employees in the company. So software to support the product, rather than software as the product
That’s a great distinction between software to support a product or workplace function vs software being sold to consumers or whose main intent is to advertise to and/or data mine consumers like my nextdoor example.