tag:blogger.com,1999:blog-124890602436915662.post4918152550107943467..comments2024-02-24T00:38:35.184-08:00Comments on Exposing Gotchas: Stop Being a Tourist!Anonymoushttp://www.blogger.com/profile/06730699060835686773noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-124890602436915662.post-48605516895224130922011-01-27T17:48:45.075-08:002011-01-27T17:48:45.075-08:00I was ready to write a long retort to your post un...I was ready to write a long retort to your post until I got to the last section: your guidelines. I heartily agree with them.<br /><br />And I also would add to your guidelines something you may have intended but not specified: Comment immediately above the code on which you're commenting.<br /><br />However--and this might come as ironic from someone that grew up in Miami, FL--tourists aren't so bad!<br /><br />We're all tourists at times. Now matter how long you've been programming in Ruby (and Rails), you will always find yourself having to immerse yourself in some other group's code. Admit it, in an environment like RoR, there is so much that happens behind the scenes, it is often difficult to follow--even with an IDE and a "fast debugger" guiding your through every step. <br /><br />Case in point: I am writing an extensive extension to Spree right now and I often hear my college professors rolling over in their graves. <br /><br />Back then you never used a variable that wasn't defined within the same file, let alone a procedure that didn't even exist at load time! Can you spell resource_controller?? I think this is an example of code generation gone wild!<br /><br />My point is, that in this environment I would never criticize anyone for writing too many comments.<br /><br />but that's me... :)<br /><br />HTH,<br />DanAnonymoushttps://www.blogger.com/profile/14869312416448386273noreply@blogger.com