Patterns are a great way to capture experience - and I’ve found that good Anti-patterns can be as effective at communicating how things should not be done as regular patterns are at communicating what should be done.

On his blog, Cameron Purdy mentions a presentation he’s giving at JavaOne 2006 entitled The Top Ten Ways to Botch an Enterprise Java Application. Judging from the comments below the blog entry, he’s going to have difficulty limiting to just ten.

For some interesting commentary on why Patterns are important, see Why Software Patterns are Important on the ReArchitecting Blog.


blog comments powered by Disqus