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."

Ajouter votre commentaire / Add your comment

Votre nom / Your name:
Sujet / Subject:
Commentaire: SPAM: Ne pas inclure de lien ou utiliser le stratagème suivant: "yahoo.com slash mapage.html"     Nous utilisons un filtre qui bloque les commentaires suspects avec une erreur 403. De même, du code de programmation ou sql peut provoquer des erreurs 403. Veuillez utiliser un lien vers votre code tel que: "pastebin.com slash jVNqLieD"    Merci! Comment: SPAM: Do not include any links in your post or use the following construct: "yahoo.com slash mypage.html"    We are using a filter that denies suspicious posts with a 403 error. Programming language or SQL code may also cause a 403 error. Please provide a link to your code instead like: "pastebin.com slash jVNqLieD"    Thank you! :
Retaper les lettres affichées / Word verification: