suppress STDOUT print ruby backticks
mechanize user agent alias list
git gc garbage collect source
There is no shame in googling. While I would heavily recommend reading and learning documentation, once you get a passing familiarity (not memorize it) you at least understand what you are using and googling it simply can save time. If you need specifics on the implementation the docs will always be there.
There is a reason we have SO and google is so great at finding things on it. Have no shame :) It doesn't make you a poor programmer to be thinking things out enough you are googling alternatives, how the innards of something works, etc.
Obviously this is all just my opinion, though. I could be a moron and not know it.
> While I would heavily recommend reading and learning documentation, once you get a passing familiarity (not memorize it) you at least understand what you are using and googling it simply can save time. If you need specifics on the implementation the docs will always be there.
And these days, the docs are usually online, and usually don't have a great dedicated search engine, so often googling is the best way to find what you are looking for in the docs, anyway.
There is a reason we have SO and google is so great at finding things on it. Have no shame :) It doesn't make you a poor programmer to be thinking things out enough you are googling alternatives, how the innards of something works, etc.
Obviously this is all just my opinion, though. I could be a moron and not know it.