Comments on: Anti-Patterns and Worst Practices – The Arrowhead Anti-Pattern http://lostechies.com/chrismissal/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern/ Thoughts while working and playing as a Software Developer Thu, 11 Apr 2013 16:53:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Chris Missal http://lostechies.com/chrismissal/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern/#comment-92 Chris Missal Tue, 02 Jun 2009 22:16:07 +0000 /blogs/chrismissal/archive/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern.aspx#comment-92 @Jaraslaw "You don't have to be a developer to feel the difference" You're right, I've seen this become a problem with HTML markup as well. @Jaraslaw
“You don’t have to be a developer to feel the difference”

You’re right, I’ve seen this become a problem with HTML markup as well.

]]> By: Jaroslaw Dobrzanski http://lostechies.com/chrismissal/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern/#comment-91 Jaroslaw Dobrzanski Tue, 02 Jun 2009 20:07:10 +0000 /blogs/chrismissal/archive/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern.aspx#comment-91 You suggestions are correct. You don't have to be a developer to feel the difference :) However, one needs to be cautious - an exception means sth wrong happened when the application was running. Therefore the number of different exceptions must be balanced. As usual there must be a compromise between nice readable code and sticking to good programming practises. Anyway, your ideas very good. You suggestions are correct. You don’t have to be a developer to feel the difference :)

However, one needs to be cautious – an exception means sth wrong happened when the application was running. Therefore the number of different exceptions must be balanced. As usual there must be a compromise between nice readable code and sticking to good programming practises.

Anyway, your ideas very good.

]]> By: SeanJA http://lostechies.com/chrismissal/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern/#comment-90 SeanJA Fri, 29 May 2009 11:35:50 +0000 /blogs/chrismissal/archive/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern.aspx#comment-90 Ah! Not the arrow! I see that way too often... especially in bad mvc attempts... sigh... Ah! Not the arrow! I see that way too often… especially in bad mvc attempts… sigh…

]]> By: Jacob Stanley http://lostechies.com/chrismissal/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern/#comment-89 Jacob Stanley Thu, 28 May 2009 09:19:16 +0000 /blogs/chrismissal/archive/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern.aspx#comment-89 @Matt I used to practice single entry/exit, but now I'm of the opinion that if you're worried about multiple returns then you should be looking at reducing the size of your methods. @Matt
I used to practice single entry/exit, but now I’m of the opinion that if you’re worried about multiple returns then you should be looking at reducing the size of your methods.

]]> By: Chris Missal http://lostechies.com/chrismissal/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern/#comment-88 Chris Missal Wed, 27 May 2009 21:53:01 +0000 /blogs/chrismissal/archive/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern.aspx#comment-88 @Tom As usual, excellent thoughts from Greg Young. So why not use an invariant rather than a validator? Cause I'm not Greg Young [MVP] ;) I think if you're debating on the kind of validation I show, and what Jeffery Palermo showed in his post, versus what Greg Young is describing, you're already better off than the guy who wrote the first couple code examples in this post. It's the thinking outside the scope of what current line you're on is what I'd like people to take away from this post. @Tom
As usual, excellent thoughts from Greg Young. So why not use an invariant rather than a validator? Cause I’m not Greg Young [MVP] ;)

I think if you’re debating on the kind of validation I show, and what Jeffery Palermo showed in his post, versus what Greg Young is describing, you’re already better off than the guy who wrote the first couple code examples in this post.

It’s the thinking outside the scope of what current line you’re on is what I’d like people to take away from this post.

]]> By: Tom de Koning http://lostechies.com/chrismissal/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern/#comment-87 Tom de Koning Wed, 27 May 2009 21:31:07 +0000 /blogs/chrismissal/archive/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern.aspx#comment-87 I normally use a validation object that I inject as well; but this post http://codebetter.com/blogs/gregyoung/archive/2009/05/22/always-valid.aspx by Grey Young made me rethink the concept of validation; why not use an invariant rather that a validator? I normally use a validation object that I inject as well; but this post http://codebetter.com/blogs/gregyoung/archive/2009/05/22/always-valid.aspx by Grey Young made me rethink the concept of validation; why not use an invariant rather that a validator?

]]> By: Chris Missal http://lostechies.com/chrismissal/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern/#comment-86 Chris Missal Wed, 27 May 2009 15:14:23 +0000 /blogs/chrismissal/archive/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern.aspx#comment-86 @Matt I agree, that usually makes it easier to understand. Clarity is always good, but so is brevity.Trying to achieve both isn't always easy, but the closer you can get to both, the better off you'll be. @Matt

I agree, that usually makes it easier to understand. Clarity is always good, but so is brevity.Trying to achieve both isn’t always easy, but the closer you can get to both, the better off you’ll be.

]]> By: Matt Youngblut http://lostechies.com/chrismissal/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern/#comment-85 Matt Youngblut Wed, 27 May 2009 14:50:57 +0000 /blogs/chrismissal/archive/2009/05/27/anti-patterns-and-worst-practices-the-arrowhead-anti-pattern.aspx#comment-85 I used to be a big fan of single point of entry/exit. Now I realize how bad arrowhead code can be. The one thing that I don't like though, is having some return right in the middle of a method (if you have small methods, this isn't a problem). I am of the belief you either exit early, or exit at the end, but not scattered throughout a method, just because you don't want arrowhead code. Sound reasonable? I used to be a big fan of single point of entry/exit. Now I realize how bad arrowhead code can be.

The one thing that I don’t like though, is having some return right in the middle of a method (if you have small methods, this isn’t a problem). I am of the belief you either exit early, or exit at the end, but not scattered throughout a method, just because you don’t want arrowhead code.

Sound reasonable?

]]>