That is the easiest strategy, but the author doesn't mean it, and the entire collection of info backs that up. He even says so a few lines later:
"This isn't one of those rants about IE6 or a campaign to try to kill it. There are enough of those around the web, but they don't help if you need to support IE6 because it still has a significant enough marketshare that you can't ignore it for business reasons. No, this is the resource you've been hoping for."
But yes, I'd love not to support IE6 in all of my work, but that's just not happening...yet.
It's often simpler, though not necessarily easier, to code a design with progressive enhancement in mind rather than graceful degradation. Designing a structure that functions properly in IE6 is not difficult.
In some cases this is impossible. I work for a company that uses a lot of internal applications that depend on old IE. Asking them to switch to Firefox is like asking them to shoot themselves in the head. A sad reality.
Amen.