[temporama1]

> the downside of adding more features is that it becomes increasingly time intensive to fix bugs, update demos, deal with pull requests and respond to questions.

Thibaut Duplessis, creator of Lichess, talks about this in a talk he gave (YouTube somewhere). He says that he's very reluctant to add new features due to the huge cost. The feature must be something very special to overcome the cost.

[baxtr]

People totally forget that new features add maintenance costs later. And I’m not only talking about business folks here but also devs.

Regarding adding features, I like the approach here: https://www.defmacro.org/2013/09/26/products.html

[gfodor]

This is a solid post - I would say tho that sometimes the right way to view product development is through the lens of media. The bucketing approach in the article breaks down somewhat if you are not directly targeting solving a problem, but creating a medium for people to solve problems using their own creativity. So the question of features reduces down to how far the feature enhances the reach of the medium, not if they are (together or in aggregate) game changers wrt solving problems, because you as the product designer are not in then business of solving the problem, the customer is.

[bcrosby95]

Yes, it's because people tend to think of features linearly. Eg "let's add one more feature". But since they tend to interact the complexity of the project grows multiplicatively.

[cercatrova]

The simplest software is no software at all. Reduce your technical debt as much as possible, and focus on simplicity. It's like the Apple principle.