Do developers over complicate things?
This is a great image taken from StuffThatHappens. It raises an interesting question and one that I think I get caught up in - "Do we offer to many features to our end user - because we can?"
Thoughts?

This is a great image taken from StuffThatHappens. It raises an interesting question and one that I think I get caught up in - "Do we offer to many features to our end user - because we can?"
Thoughts?

The second cause is usually the screen on the bottom is an application that's 5 years old and on it's 100th minor revision to get something done for a meeting, show, etc.
Years ago I worked for a B2B travel company. We had a home-grown programming language that powered our web application. One code base ran 50,000+ sites. A site's admin user had a toggle for everything under the sun. Marketing called them "nice to haves".
When we dug into the application to start planning a conversion to a J2EE application, three of us indexed the whole admin section. Our DBA Manager then went into the database to see how many options across all of our sites were changed from the default.
Out of around 40,000 options (I kid you not), only about 200 -across all of our sites- were not set to their default values.
The J2EE application started out with about 150 options available to the site admin. Marketing just had to deal with it.