The trouble with avoiding "all right-thinking people know" is that I have no idea how to find a solid citation for the claim that, say, software engineering is at least as much about people as things. It's a thing you will find anyone senior who's good at their job to agree with. Would you accept books by experienced software engineers as evidence of this point?
Once you grant that point, much of the argument falls apart, as it's clear he's arguing about very junior-level coding and not software engineering as a whole.
I am senior at my job and I disagree with that assertion. People skills are indeed helpful and a good benefit, but they are nowhere near primary. Consider the following two people:
(A) Understands people hardly at all, is constantly confused by hem, but understands computers very well
(B) Understands computers hardly at all, is constantly confused by them, but understands people very well
Which of these two candidates is going to be able to design and build a complex software product?
B, without question! You have junior people to get unconfused by computers and tell you what they're capable of. You have a wealth of existing open-source libraries, protocol designs, whitepapers about private products, etc. You need to understand what the documentation of those products are, that is, what humans are claiming about those components and what humans have successfully done with them. You don't need to be able to tell a double from a lambda to design and lead a team building a complex software product.
Candidate A is going to build a technically impressive product, sure, but we have no idea whether it's what the customer wanted. Candidate A will be a fantastic research scientist or lone-wolf open source hacker, but not a product builder.
The trouble with avoiding "all right-thinking people know" is that I have no idea how to find a solid citation for the claim that, say, software engineering is at least as much about people as things. It's a thing you will find anyone senior who's good at their job to agree with. Would you accept books by experienced software engineers as evidence of this point?
Once you grant that point, much of the argument falls apart, as it's clear he's arguing about very junior-level coding and not software engineering as a whole.