There are people who are bad at every job. That doesn’t mean that the people who are hiring people into that role are looking to have someone do it badly. Or t

There are people who are bad at every job. That doesn’t mean that the people who are hiring people into that role are looking to have someone do it badly. Or that anyone who wants such a role is automatically suspected of having nefarious motives. These role archetypes are descriptions of realistic, reasonable expectations for high level IC roles. It’s a useful, positive contribution that will help engineering directors and senior coders better negotiate clearly defined roles and responsibilities. It’s just not constructive to say ‘but yeah, sometimes when you employ someone at this level and you don’t clarify the role or hold them accountable, they do terrible things and it enables charlatans to prosper!’ Sure, of course it does. But this article is a useful and constructive model for helping prevent that from happening. What you frame as an addition to the article actually represents a cynical undermining of its entire value. I think that’s a sad way to engage.