I believe that your response is as important as the original article itself.
I am one of the Ricks (albeit with a MUCH better attitude towards others). I consider myself a strong team player (I have created ones myself), and I like talking with people.
But I also love to code. I am doing this since I was 12 as a hobby, and I am still doing it (it became a proffession). And after 11 years in the industry, in my early thirties, I find myself thinking the EXACT same thing as you do.
I find myself being tired of an industry promoting mediocrity, and also other people that think are entitled to a hard-acquired experience and knowledge, in the same way they feel entitled to a google result.
Therefore, I strongly agree with you in the analysis of Rick’s phsychology. I also sympathize with Rick in a way, and I wholeheartedly agree with you at all your points.
But I also think that senior and developers should help / lead by example, and not by actually doing the work of others. Lead / senior devs are not university professors, they should be role models. Worse than Rick exploding on the rest of the team the way he did, is Rick never leaving his office as a lead developer and never talking with his team at a proper professional level. That was part of his job description as a Lead Developer and he stopped doing it according to the article. Therefore, the project was on the verge of failure not because of what Rick did, but because of what Rick didn’t do.