I don't think any of these are anti-patterns. They are behaviors that may be completely reasonable to use in a given circumstance. The author is misapplying software engineering terminology to software engineering management.
Actually, I used the terminology that Hoffman and Cantrill used. The point is not that the behaviors are unreasonable "in a given circumstance" but when applied continually.
Then you have to define "continually." It's probably better to say it's unreasonable when it eventually fails, but you can only make that determination after the fact. The truth is that any managerial behavior, when applied continually, will become an anti-pattern. So choosing particular behaviors, organizing and labeling them is just an autistic exercise.
