Software Development with Linux

To have success know why it was a success

SUN, 01 NOV 2009

In the history of the humankind, the thought of one solution that would fit for all, that would be perfect for everybody, have often surfaced.  The many empires along the time, the religions, all encompassed that idea that what worked for them was the best solution and should be used by everyone.

The same thing have happened and is still happening in the computer science field.  Every time a new software development methodology, coding/testing/debugging practice, project management techniques, programming language, software/hardware architecture, etc., make the news, you get people swearing that this novelty is the way to go.  If you're not doing it exactly as evangelized, you're doing it wrong.

Well, at last, some people don't fall for that.  Like Scott Ambler, who says that every IT project is different in some way, as snowflakes, so any agile methodology used should consider the particularities of the project.  Like Johanna Rothman, who ask if three backlogs could be better than one.

To have that kind of reflexion, you need to understand why a particular procedure, solution, or method was invented, and why it worked for someone.  If you don't know why it worked somewhere, how do you know that it will work for you?
Don't follow any advice, no matter how good, until you feel as deeply in your spirit as you think in your mind that the counsel is wise -- Joan Rivers, American comedian
If you cannot explain why your methodology work for you, and in which case it would not work, you're doing it wrong.