The captions are hyperbolic and quite funny, but perhaps funnier is the fact that our unconscious brains do have these kinds of reactions (though muted, of course).
From an article I read the other day:
"The cognitive revolution of the past thirty years provides a different perspective on our lives, one that emphasizes the relative importance of emotion over pure reason, social connections over individual choice, moral intuition over abstract logic, perceptiveness over I.Q."
I've found myself in the situation, a few times, where it was necessary to run `bundle update' to resolve dependency conflicts. You should, of course, always thoroughly test your application before deploying production code after a `bundle update', but I'd hardly tell people to not "ever" run the command, especially if you have git-based dependencies that need to be updated.
Just to clarify, you can always run bundle update for a specific gem, instead of for every gem in the Gemfile (this is the behavior if you run the command without any arguments). Recent versions of bundler (>=1.0) are pretty good about telling you exactly which gems have dependency conflicts, so it should be pretty easy to determine which gem to pass to bundle update.
Maintaining a voice is important, and style guides and guidelines are important in enforcing this; plus, most of the content herein is what _not_ to do rather than what _to_ do, so it's more about what the cookie cutter isn't cutting than what it is.
From an article I read the other day:
"The cognitive revolution of the past thirty years provides a different perspective on our lives, one that emphasizes the relative importance of emotion over pure reason, social connections over individual choice, moral intuition over abstract logic, perceptiveness over I.Q."
- http://www.newyorker.com/reporting/2011/01/17/110117fa_fact_...