Open source, not open contribution

Feature Liabilities

Ben Johnson shares his perspective on why features can be liabilities, especially in database management. He explains that while features are often seen as assets, they can introduce complexities and potential issues, such as corrupting a database. Ben emphasizes the need for the utility of a feature to significantly outweigh its liabilities to justify its inclusion 1.

Every little feature I add is something that could possibly corrupt a database. It's really pretty serious.

--- Ben Johnson

He also highlights how features interact with each other, leading to unexpected challenges that can grow exponentially, making them difficult to manage and remove 2.

   

Strategic Decisions

The analogy between hiring and feature adoption underscores the importance of strategic decision-making. Adam Stacoviak draws parallels between being cautious with hiring and being selective with feature adoption, as both require careful consideration to avoid future complications 3. Ben agrees, noting that while new features can be exciting, they often bring unforeseen challenges that can lead to regret.

For every feature or for every hire, you may have to eventually deprecate it or fire them or circumstances change.

--- Adam Stacoviak

This approach emphasizes the need for calculated decisions to ensure long-term project success and maintainability.