I have read this question and after a very long time it's clear I still don't understand anti-patterns. perhaps, it raised a new level of curosity to know why should I read Anti design pattern if they are actually nothing but a Bad Practice. Is there any chance I should implement those anti design patterns in my application ?EDITWhen Jeff said: A basic rule of  programming is to never write what you  can buy or get for free,.Which I believe is the way to implement copy & paste programming then should I say that SO is ,in some way or another, following Anti-Pattern?
Anti patterns - Worth spending time or not
architecture;design patterns;anti patterns
why should I read Anti design pattern if they are actually nothing but a Bad PracticeIt takes one to know one. If you don't read about them, how can you know if you are using them?When Jeff said: A basic rule of programming is to never write what you can buy or get for free,.Which I believe is the way to implement copy & paste programming then should I say that SO is ,in some way or another, following Anti-Pattern?Copy-paste programming is when you take something and use it without trying to understand what it does.Always get at least a general understanding how a snippet/framework works before you use it.