Development
For a quick example, see the website's featured Development AntiPattern, Lava Flow.
The first development AntiPatterns came from Mike Akroyd, a consultant who worked with Motorola and other large firms on classic problems in object-oriented design. Every one of his AntiPatterns came with a refactored solution attached. Name the problem, then say how to get out of it.
An AntiPattern that only names the negative solution, with no path out, is a pseudo-AntiPattern, closer to a complaint than a diagnosis. A key goal of this chapter is software refactoring: changing code's structure to support extension and long-term maintenance without changing what it actually does.