3 ms·
Features don't necessarily translate into more complexity.
by Duff 15y ago
Features don't necessarily translate into more complexity.
- revorad 15y agoActually, they do by default. It takes extra work to maintain simplicity while adding features.
- mcgwiz 15y agoThis was implied by Duff's use of the word "necessary" [sic]. I believe his point was that it's possible to have features and complexity. So although you're right that providing both simplicity and feature-richness is not free, the companies that can afford both (assuming the features address actual problems, or even just pain points, that customers have) are going to fare better than those that don't.
- Duff 15y agoSorry about my mangling of the english language! From the end user's perspective, features often reduce complexity, sometimes dramatically so. Before "mail merge" was a common MS Word feature, collating form letters was a tedious job. Good engineering and design integrates features into the application in a way that avoids complexity.
- ams6110 15y agoYet even something as straightforward as mail merge is a hurdle many MS Word users cannot clear, at least not without out a call to the help desk.
- draggnar 15y agocomplexity for you does not mean complexity for the user
- revorad 15y agoI'm only talking about complexity for the user.