« TechEd 2009 | Main | Paul Glavich: Performance Testing and Optimisation »

Tuesday, 15 September 2009


TrackBack URL for this entry:

Listed below are links to weblogs that reference What’s In a Method?:


Feed You can follow this conversation by subscribing to the comment feed for this post.

An anti-pattern ???

I can understand the value of doing this to the entry points (e.g. from the UI) to a complex business object to handle business rules violation - but to a simple helper method? Overkill!

Wouldn’t it fall into the following categories … ???

Gold plating: Continuing to work on a task or project well past the point at which extra effort is adding value
Accidental complexity: Introducing unnecessary complexity into a solution
Cargo cult programming: Using patterns and methods without understanding why
Expection handling: (a portmanteau of expect and exception) Using a language's error handling system to implement normal program logic
Source: http://en.wikipedia.org/wiki/Anti-pattern

I’d be fascinated to know what others think – and more fascinated to know what they’d do ;)

:) Hey Chris. This was merely an example dude. If I end up doing this daily on every method I will end up with nothing being delivered. I though the simple method would help me get my point through and I understand you're every concern if it was a regular practice. :)

The comments to this entry are closed.

November 2010

Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30        

Twitter / OmarBesiso

Blog powered by Typepad