“If something is too complex to understand, it must be wrong”

An article, posted more than 3 years ago filed in , , , , & .

While looking for the source of another quote (something along the lines of “If it takes you too long, you're probably doing it wrong”, which I recall having picked up in the Rails community (if you recognize it, please let me know)) I found the following bold statement. We're not talking science here, we're talking software development (actually this guy is talking Java Spring development):

> “If something is too complex to understand, it must be wrong”

from Arjen Poutsma

Some background on this quote can be found on this Xebia website.

Yep, I'm working on a project that seems to have grown way too complex for what it actually should have been.

Happy coding ;)

Continue reading...

Mobile feature creep

An article, posted about 12 years ago filed in , , , , , , , & .

In this text causes and effects of feature creep in mobile telephones are being discussed. The problem with feature creep is that adding more features makes mobile telephones harder to use. Instead of paying attention to the ease of use of a telephone, most companies are only concerned with offering more features than the competitor. And the customer is debit to this behaviour.

Customers want features and therefore companies are offering them features. And since the competition can always offer more features, thus making their phones more attractive to the customers, all competitors try to stay ahead, giving rise to even more, seemingly needless, additions.

Due to the increasing number of features mobile telephones are also becoming increasingly hard to use: there is an inverse relation between the two. This inverse relationship can be demonstrated by making the one of the most simplest devices more complex: light switches. One light switch on a wall is simple to operate, yet…

Continue reading...

murb blog