I guess with discipline I can train myself to always think about things like the rhythm created by font-size and margins on headers, but I've not experienced the downsides of a full reset yet.
And I'm not sure why a CSS reset would make you consider each design decision; most design work should be done prior to coding, and its a rare instance that I don't replace most defaults.
As apposed to having to to declare a reset, and then re-declaring everything again.
He says this in the article too: "Approach 1: use normalize.css as a starting point for your own project’s base CSS, customising the values to match the design’s requirements."
The point of normalize is not to keep links blue, and buttons gray. They find the rendering discrepancies between browsers, fix them, and make it easy for you to change.
normalizations are all about memorization, ie default for h1 is A h3 B. To me this is far more complicated than deciding i want X, what do i need to do to produce that. maybe a little extra typing, (probably a trivial amount for a website or web app of any complexity).