And they don’t need to read anyway, because comments are the real reason people come to a site like this. If the comments praise the article highly or make strong references, then perhaps it warrants a read, otherwise the comments make for much better content. You can often tell what the article’s main idea is from the headline anyway, otherwise it’s just a bad headline and probably a bad article.
Obviously, as nearly any reader would grant, there are other dimensions like business acumen, network connections, market timing, etc., that matter hugely in the specific story of Bill Gates, and clearly the article does not have as a goal a desire to discuss all those different dimensions as much as discussing labor productivity.
And that’s fine.
Some essays may focus on one of these aspects or another. This one happens to be among the subset that focus on labor productivity, which is a valid and worthwhile subset of factors to spend an essay focusing on.
I'm afraid if we run a proper statistical analysis of programming labor vs. the result, we'll see a pretty strong correlation between the two.
There will be outliers, but according to my personal (non-scientific) observation, "negative" outliers are extremely rare: I know very average software developers who raised to the top overtaking their smarter colleagues. I still have to see a great developer who due to the lack of opportunities cannot make ends meet.
Separately to your second point, I think you’re just badly mistaken. Firstly, meritocracy would mean someone receives financial compensation directly proportional to their productivity. I don’t know any software developers for whom this is remotely true. Often developers are paid a tiny fraction of the revenue they generate, nothing remotely approaching a fair fraction from a meritocratic point of view.
Secondly, there are many skilled software developers who cannot find work and cannot find competitive wages. Some end up unemployed from chronic burnout or the toll that dysfunctional open plan work environments take, some have family circumstances requiring them to live in places where the job markets are poor, some are unemployed after being fired for ageist cost cutting, and some work for successful companies but are deeply exploited, earning a fraction of what the person in the next cubicle is earning, despite being equally productive.
It’s really harmful to propagate this stereotype that just because a person had training or skill in software engineering, they have a simple path to a middle class life. Absolutely not true.
I would call this a bad strawman of meritocracy if you weren't obviously for meritocracy. The parts I object to are "directly proportional" and the assertion that "a tiny fraction of the revenue they generate" is not "a fair fraction from a meritocratic point of view".
And if they are really a skilled developer whose productivity is sincerely a large multiplier beyond their peers’ productivity, they’ll be lucky to earn even 30% more, despite literally accounting for 10x, 100x, 1000x more revenue.
I do not see how any rational argument could be made to suggest this is even the tiniest bit meritocratic. And we’re not even discussing the role of political favorites or nepotism might play in bonuses or promotions, etc. etc.