I think the article mixes different things.

> That’s the way we’ve always done it.

That's not ego, that's laziness. At least based on experience, engineers are reluctant to change simply because they feel comfortable enough with their codebases.

> Assign it to me. Nobody else will be able to fix it.

Yep, that looks like ego.

> This feature is too important to assign to the junior dev.

Bad communication style perhaps? There are features that require a senior to drive them. What's wrong with that? Sure thing, I wouldn't phrase it as the author, but I don't see the ego anywhere. I see transparency and being upfront.

> We should start using this new tool in our pipeline

Again, perhaps it's just bad communication style. An engineer that says this is someone who cares enough to suggest things, even when nobody is asking. I know engineers who never suggest (or gatekeep) anything, they simply don't care