Good question! For me it really depends who I am communicating with, and what I'm trying to communicate. In this manner, wireframes (of various fidelities) can be useful for illustrating a quick concept to the design team, or having some editable resources on hand that can be adapted as needed for a large or ongoing project.
If I'm working on a prototype, I've pretty much always done wireframing of some sort on those screens beforehand - often hand sketches or Balsamiq mockups. I include prototypes in most of my projects - mostly because I like bringing development and design together, and because I like the way Stakeholders can also see the product coming together on screen (rather than on paper) but obviously this depends on the creator's code literacy, where decisions are yet to be made, and the complexity or otherwise of what is being produced. Prototypes also become more useful for me when working on flow and interactions, and when putting things in front of a test participant (whipping paper prototypes around isn't always ideal).
I think Garett's article is actually a great articulation of the key points. What stood out for you?