I think the point of this article is that because of Coffee's wide use, developers will often find themselves in a situation where they can't "just don't use it".

You could say "don't take that job", but I think the point of the article is to make it clear that CoffeeScript is not an unvarnished win, and that choosing to use it will result in otherwise qualified people taking your advice and not wanting to work on your project.