Printing out can be helpful for really gnarly code. I used to do it a lot more - even with your own code, you sometimes see it in a different light on paper.
mark On Fri, Feb 12, 2010 at 3:34 PM, Ryan Bigg <[email protected]> wrote: > I agree with going through the code and reading the tests (again "there are > tests, aren't there?", aka TATAT). If the application is a bit light on > tests ask them what they spend most of their time as that's probably going > to be where you're going to spend most of yours too. See a bug? Write a test > to cover it, THEN refactor. > Yay for parroting. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- A UNIX signature isn't a return address, it's the ASCII equivalent of a black velvet clown painting. It's a rectangle of carets surrounding a quote from a literary giant of weeniedom like Heinlein or Dr. Who. -- Chris Maeda -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
