At the final presentation of our XP-driven webshop project we ended up in a discussion about whether to catch runtime exceptions at the top-level or not. After having attended a talk by Kåre Nilsen at ROOTS 2009, called “Enterprise app without enterprise crap”, we took the stand that we did not want to catch the exceptions and rather try to fix them if they occured in stead of hiding what went wrong.
It turns out there is an anti-pattern that describes this dilemma, called the Diaper Pattern. -”Because it catches all the shit”.
Now what’s left to decide is whether this applies to web apps or not…
The Diaper Pattern
At the final presentation of our XP-driven webshop project we ended up in a discussion about whether to catch runtime exceptions at the top-level or not. After having attended a talk by Kåre Nilsen at ROOTS 2009, called “Enterprise app without enterprise crap”, we took the stand that we did not want to catch the exceptions and rather try to fix them if they occured in stead of hiding what went wrong.
It turns out there is an anti-pattern that describes this dilemma, called the Diaper Pattern. -”Because it catches all the shit”.
Now what’s left to decide is whether this applies to web apps or not…
No related posts.