A lot of software developers are seduced by the old "80/20" rule. It seems
to make a lot of sense: 80% of the people use 20% of the features. So you
convince yourself that you only need to implement 20% of the features, and
you can still sell 80% as many copies.
Unfortunately, it's never the same 20%. Everybody uses a different set of
features. In the last 10 years I have probably heard of dozens of companies
who, determined not to learn from each other, tried to release "lite" word
processors that only implement 20% of the features. This story is as old as
the PC. Most of the time, what happens is that they give their program to a
journalist to review, and the journalist reviews it by writing their review
using the new word processor, and then the journalist tries to find the
"word count" feature which they need because most journalists have precise
word count requirements, and it's not there, because it's in the "80% that
nobody uses," and the journalist ends up writing a story that attempts to
claim simultaneously that lite programs are good, bloat is bad, and I can't
use this damn thing 'cause it won't count my words. If I had a dollar for
every time this has happened I would be very happy.
Joel Spolsky
"Strategy Letter IV: Bloatware and the 80/20 Myth"
to make a lot of sense: 80% of the people use 20% of the features. So you
convince yourself that you only need to implement 20% of the features, and
you can still sell 80% as many copies.
Unfortunately, it's never the same 20%. Everybody uses a different set of
features. In the last 10 years I have probably heard of dozens of companies
who, determined not to learn from each other, tried to release "lite" word
processors that only implement 20% of the features. This story is as old as
the PC. Most of the time, what happens is that they give their program to a
journalist to review, and the journalist reviews it by writing their review
using the new word processor, and then the journalist tries to find the
"word count" feature which they need because most journalists have precise
word count requirements, and it's not there, because it's in the "80% that
nobody uses," and the journalist ends up writing a story that attempts to
claim simultaneously that lite programs are good, bloat is bad, and I can't
use this damn thing 'cause it won't count my words. If I had a dollar for
every time this has happened I would be very happy.
Joel Spolsky
"Strategy Letter IV: Bloatware and the 80/20 Myth"
Related:
- bug n.
An unwanted and unintended property of a program or
piece of hardware,
esp. one that causes it to malfunction. Antonym... - talk mode n.
A feature supported by Unix, ITS, and some
other OSes that allows two or more logged-in users to set up a
real-time on-line conversation.
It combines the immediacy of talking with all the... - Pareto's Law (The 20/80 Law)
20% of the customers account for 80% of the turnover,
20% of components account for 80% of the cost, and... - Long's Notes
1) Always store beer in a dark place.
2) Any priest or shaman must be presumed guilty until... - warez d00dz /weirz doodz/ n.
A substantial subculture of
crackers refer to themselves as `warez d00dz';
there is evidently some connection with B1FF here... - EVERYTHING I NEED TO KNOW I LEARNED IN CORPORATE AMERICA Part 2 of 2
17.
All things being equal, fat people use more soap. 18... - The 20/80 Law: 20 percent of the customers account for 80 percent
of the turnover,
20 percent of the components account for 80 percent... - The following appeared in a letter to the editor of the Walnut Grove town newspaper.
"Walnut Grove's town council has advocated switching... - As many of you know, I am taking a class here at UNC on Personality.
One of the tests to determine personality in our book...
