We have a Patterns Panacea effect when we forget the first rule of XP methodology: simplicity  and we want to use a pattern in any case. We need to relax our mind and choose the easiest way, it will be the better way. If in the future we need to change it in order to remove some duplicates or some overload we will refactor it.   The Under-Engineering is far more common than Over-Engineering. When we produce poorly designed software we under-engineer. The big problem of under-engineering is maintaining the software we have producted....

I was reading the book of Martin Fowler: Refactoring to Patterns. Just on the first five pages of this book there are so many information to think about. One of these is the Over-engineering terminology. The Over-engineering word means: When you make your code more flexible or sophisticated than it needs to be, you Over-Engineer it. Some programmers do this because they believe they know their system's future requirements. If your predictions are wrong, you waste precious time and money. What typically happens with code you produce in anticipation of needs that never...

I'm a fan of xp methodology, and I am studying and using it a little at a time.   One of the questions I do to myself in these days is: What is the difference between SCRUM and XP? I have found some answers in Martin's article: http://martinfowler.com/articles/newMethodology.html How Martin wrote the big difference are: Scrum concentrates on the management aspects of software development Scrum dividing development into thirty day iterations (called 'sprints') and applying closer monitoring and control with daily scrum ...