Sometimes I encounter a typical example of what I call “over-engineering”. Someone has been enthusiastically designing a webpage, and added a few business rules too many.

The example below could have been funny if the consequences weren’t so dangerous.

I was creating an account on the Vodafone 360 site. When I provided my password, I noticed they had a “password security indicator”. I was also pleased to see that I entered an extremely safe password; 4 out of 4!!
Then I got this message:

how not to restrict a password

So, my password is restricted to digits and characters only. And apparently, only capitals too. Isn’t that odd? It severely restricts me in providing a safe password, and it violates every guideline ever created about passwords.

Shouldn’t any designer who thinks of such a rule shouldn’t be fired on the spot? I mean, what was he thinking?

Tagged with:  

2 Responses to A classic example of over-engineering your software

  1. Arjaan says:

    Not the programmer (or two seperate programmers implementing the two business rules), but the designer, tester, project manager AND the customer all should be punished in a terrible way for not thinking and communicating..

  2. Patrick Sinke says:

    Amen :-)

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>