Except that the featured article isn't saying not to worry about testing at all, it's about how to actually get value out of your testing.
I guess the main reason for my condescending sentiment is due that the author gives 0 examples of code that requires tests vs code that does not so it is actually not.