Software Feature Creep
The cluster debates the merits and risks of adding new features to software products, including feature creep, prioritization over core improvements, user requests, and management incentives.
Activity Over Time
Top Contributors
Keywords
Sample Comments
It's not even an attempted bait and switch. They thought that a certain feature was needed/wanted, so they tried implementing it. Extra features have killed projects before and will kill in the future.
What's wrong with having a need for a feature and wanting it implemented?
Adding frequently requested features to your product is now "desperation"?
Yes, but don't you solve problems by implementing features?
Suggestion: before adding other features, add the features you really need. Chances are, others need it too.
Let’s ship features! To heck with what users may need or want!
It doesn't make much sense for developers to spend time adding features that users cannot use.
It's kinda related to bikeshedding, do anything else than pushing features
I'm on board with this, imagine the headaches and development costs of adding this feature and 100 other QoL features. It would absorb energy and complexity budget that could be spent on core product features.
I understand the incentive and pressing need from the dev perspective. but shouldn't the management say "no this feature is an overhead".