The quote you pulled out boils down to something even simpler than that: People who are good at programming aren't necessarily good at designing API's.

I think there's a kernel of a valid point underneath. A macro necessarily has a larger (potential) interface surface than a function, because there's less you can take for granted about how it interacts with the rest of your code. And I agree, API design is a specialized skill that requires quite a bit of thought.

But I agree with your conclusion more than his: This is to take care with macros, not a reason to shun them altogether.