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.

Comments

blog comments powered by Disqus
Next Post
Appropriate Expertise  26 Feb 2006
Prior Post
Site Restructure  30 Dec 2005
Related Posts
Using Constructors  27 Feb 2023
An Inconvenient API  18 Feb 2023
Method Archetypes  11 Sep 2022
A bash puzzle, solved  02 Jul 2022
A bash puzzle  25 Jun 2022
Improve your troubleshooting by aggregating errors  11 Jun 2022
Improve your troubleshooting by wrapping errors  28 May 2022
Keep your promises  14 May 2022
When are you done?  18 Apr 2022
Fixing GitHub Authentication  28 Nov 2021
Archives
February 2006
2006