Hypothetical example. Your employer has 1 billion users. You create compression that cuts down storage costs by 4%. Run the math and you see how much you saved.
If you saved $0.01 per user, you saved $10m. If the average salary is 100K and you saved $10m, you performed at 100x.
I agree the potential for "X" performance is hard to spot or measure when one isn't in proximity to big problems.
Things are accomplished by teams, not individuals.
There was always a huge amount of players at work helping the upper execs and sales teams, from the devs to HR.
I guess OP's post was and the article itself are noting that working your ass off and making a big contribution in SV as an engineer can sometimes be a bad deal, especially when the engineer in question really is talented.
With a small experienced team and proper division of lager into vertical slices, that can be done.
Honestly? Yes.
I have no idea how many dollars of "revenue generated" or "cost saved" are attributable to me as individual. Or anyone else.
Using lines of code as a performance metric? Get ready to see a multi-line Javadoc on every local variable, or get ready to see some insane Perl-style one-liners, depending on how you're using the LOC number.
"Time needed to deliver work"? Again, what is "work"? If your data consists of JIRA tickets, then get ready for a culture of writing JIRA tickets at a contrived (and inefficient) micro level of granularity.
There's no good way to objectively measure your "value" at your CURRENT company. And what do I do when interviewing you to come here for your next job... just take your word for your measurements at the previous gig?
Out of curiosity, are you a programmer? Because subjectively making stuff up, while under the honest delusion that you're guided by objective numbers, is the single most "MBA" trait there is.