Write tests, write code.
Later: Write code, break tests. This is the part that saves your ass because if you're deploying WITHOUT tests you're probably thinking "MY APP IS BULLETPROOF" when actually it's "BULLET RIDDEN". So, if you have tests you'll see that something is FUBAR'd and you'll really want to fix that before deploying, therefore making you feel great that you're doing a little work to keep the world safe and your clients happy that their application is not broken. ----- Ryan Bigg Freelancer http://frozenplague.net --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
