|We have been knowing for a while about development patterns, let's now look at anti-patterns!|
More simply put, anti-patterns define what not to do!
Oh well, I have always though that it was better to teach what to do instead of teaching what not to do but this is nevertheless an interesting thing to read. Have a look at the links below which point to documentation about anti-patterns from IBM.
One of the listed anti-pattern is "infrequent check-ins". What about projects that have no source control at all? ;-)
"While Continuous Integration can be extremely effective at reducing risks on a project, it requires a greater emphasis on your day-to-day activities related to coding. In this installment of Automation for the people, learn how to lay out a series of CI anti-patterns, and more importantly, learn how to avoid them. For more Java resources, and to specifically learn more about Java Testing and Debugging, take a look at this developerWorks Space."
|Mis à jour / Last updated ( mercredi, 26 mars 2008 23:46 )|