Quote:
Originally Posted by chaley
Of course, Kovid could refuse to accept my changes, but why should he do that? The functionality is useful to some number of people. Refusing to integrate it would tell me to go away, and tell the "some number of people" that their needs don't matter. These are the people who engage with me, who work with me, and who in the end matter to me.
|
That's the perfect recipe to build an unmaintainable software, saying yes to every feature because someone has asked for it. I don't know which features did you implement, so this is just a general thought about usability and how to grow a software program. You shouldn't add a feature until many many people has asked for it. If Calibre has 6M users, you shouldn't add a feature unless is going to be useful to at least 2M.
That's what theory says to avoid having thousands of features that get mixed, that produce bugs, that have to be maintain or that complicate the interface.
I highly recommend you all should read the book 'Getting Real', specially this chapter
http://gettingreal.37signals.com/ch05_Start_With_No.php. It applies very well in this case
