Oh, one more thing: One of the biggest things I find myself googling is testing. Because so much magic happens, I am always googling to find out "how do I test this?!" I seem to come up with testing gotchas and problems all the time.
Googling about testing actually results in very poor results. For example, if you google testing validations, you will come across Ruby 2.0 testing code that is obsolete... or you'll find a way of testing that doesn't cover all the cases and is kind of bloated. You'd think one would not have to reinvent the wheel about "how to test validations", but that's actually what happened in my case (my solution I coded myself is rather quite nice... I wish I saw it online though :/) Once you throw in Devise into the mix, testing gets even more complicated. For example, devise gives you the necessary methods when testing controllers, but will not include them for Helpers - even if you specify that it should. It's really very odd behaviour. This type of random "doesn't just work" situation seems to happen all the time for me. Anyway, maybe now I am just venting. I am finding the whole "learning a new platform" to be perhaps a lot more work than I thought it would be. I'm starting to think a "bloated Java programmer who's REALLY good at that bloat" can probably still produce faster than someone learning Rails. Of course, eventually, the Rails programmer will outpace him... but it might take awhile. -- 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.
