When to use CSS Reset Method

One way to look at it is if you're doing a large project, like the Oregon Health Plan site, then reset.css is the way to go as you're leaving nothing to chance. You're nuking it and rebuilding upon the ashes.

Normalize.css assumes that you're zeroing out the more common elements bu still want to preserve the useful ones, like tables and <input> for example. Normalize.css, based on my experience and my web dev teacher, is that it tends to make things look and act like they do in Google chrome. I've made one or two websites where it didn't quite work out if I used firefox or opera instead, but I think this will be a rarity. For the majority of your uses, you should be ok with Normalize.css

Yes you should always use a reset method.

Due to lack of standards around it, each browser manufacturer creates their own styling for their browser, leaving each browser's default base rendering of elements different. This, of course, causes inconsistencies across browsers that must be fixed. - http://pointnorth.io/#styling

So I should always use reset and normalize? It seems to me that using Normalize only can be just as effective.