Programming Limericks
November 4, 2007
GOTO Considered Harmful
GOTO makes your code like spaghetti
Please don’t throw it around like confetti
A conditional clause
Has far fewer flaws
So just structure your program, already.
Good Agile, Bad Agile
It’s hip to use Agile scrums
To prepare for change (when it comes)
But, frankly, it seems
To be harmful to teams
Excepting my Googler chums.
What’s Nu?
We fused Cocoa’s power with Scheme
To produce a language supreme
Of glorious beauty
That kicks Ruby’s booty
And makes Python look powered by steam.
Entry Filed under: code. .
2 Comments Add your own
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed
1.
Alex Gordon | November 5, 2007 at 9:36 am
I’ve found that goto is OK, as long as you obey one rule.
Only jump forward, not backwards.
Then it becomes *very* useful, and all the bad side effects just go away.
2.
Burt Reany | November 12, 2007 at 7:36 pm
Structured code (recursive over recursive) good; “linear structured” code (directional over recursive) bad. ANY difference of opinion is apostacy. Heresy.
(Where in the name of Altered_GoTo was this first documented?)