I agree, this is probably because we never 'speak' (although write) in programming languages trying to convey something. This goes same for 'hearing' (although we read and understand, hopefully). We always use human languages for those purposes, well, except for those times we speak in pseudo-code.
These are borrowings or coins into a natural language. A word from bash does not mean you are speaking bash any more than saying macaron would mean you are speaking French.
Don't be too quick to take it at face value. It's hard to write down what is actually in one's head, even for experienced writers. I'm sure he'll tell you a lot more on the stuff he claims he doesn't know if you had the good fortune of having a chat with him in person. Also, keep in mind that he probably knows deeply about some things and their extents, and so his definition of words like 'fuzzy' should be different from that of an intern's. As he puts it himself,
> Experienced developers have valuable expertise despite knowledge gaps
But it's not that simple. There are many things like social dynamics at play whenever people interact with one another, and the one with most charisma is going to be a leader without a title–and that can be good too.
Neither regular management is. There's plenty of stories of failed management. At least if it's a whole team doing the management, toxic behavior by one individual can be controlled. If the toxic individual gets to be manager instead, then there's nothing to stop him.
And companies who dare asking your consent to collect, retain, and share (with 3rd parties they like) everything about you from your teams chat to gene data.
