It's pretty depressing how many of the comments are purely answering the title and not discussing the content of the article. In particular, the comments seem mostly focused on consumer product build quality whereas the article is more focused on e.g. businesses trying to outsource something (like same day delivery) and getting a worse result even when they pay more than doing it internally. And the cultural obstacle…
> I will note that I often wish Dan Luu was a bit less apparently-uniformly-confident in some of the statements he writes. He does back up what he says, but he'll use the same tone for something he's seen anecdotally and something he's spent a month personally investigating. Dan Luu is one of my favorite currently-active bloggers. He's obviously a smart person with a good amount of experience in specific areas. Howev…
I don't think Dan Luu is struggling for work.
So the question is do you want to hire someone like Dan Luu or not? If the answer is yes, then you might want to consider how your interview process might interact with such a person. If you are thinking from the perspective of someone doing the hiring (as those articles seem to be), it is nonsensical to simply respond by saying "well, the candidates just need to be more submissive and compliant to whatever our process is."
Perhaps Dan Luu is a unique snowflake and/or nobody needs to hire someone like that. Or it could be that there are quite a large number of developers with attitudes and experience that lead to similarly unproductive or inefficient interactions with tech interview processes because those processes may be fixating on having the candidate do a specific performance rather than trying to understand what individuals can offer and whether that would be useful when added to the existing team. It could be that such developers would be as good or better fit, in a lot of cases, than people who can do oscar-winning interview performances.