I think the article has it right when it referenced the importance of "the ability to reward engineering work that had little visible outcome". Rewarding mostly shipping (or launching) seems to be broken in particular, I'm not sure rewards themselves are entirely ineffective.
I've fallen into this kitchen-sink trap in the past. Though I think it's tough for stakeholders to appreciate the invisibles like security or reliably until those get bad enough to cross a critical threshold.
My resume would be fine if I “played ball” aka. was an opportunistic smiling liar. Back in my old market we could give 4 week notice and say we were interviewing around, here they treat you like shit and terminate when you express need for rest/thoughts of change. I understand it from a fear/risk point of view, unsure how to change that besides refusing to play (eg. starting the next unicorn out of pocket as a B corp, making investors take a whiteboard exam before having a phone call with leadership :).
Money isn’t a motivator, contrary it makes the treadmill go faster if we aren’t anticipating how to make it work for us rather than help us consume ourselves in desire and lust. A steady business with an understandable revenue stream, imagine the anxieties we wouldn’t have.
Are you saying that an investor who can, say, write out FizzBuzz in JS would be a better partner? Or are we talking about a different set of whiteboard-able skills?
Now the problem with 6 months is that the engineers typically leave after launch once their target of raise and promotion is met and the company suffers to varying degree. In the long run this may or may not matter depending upon external factors - for ex. cloud services kick-off helped Amazon a lot so even if there are significant number of engineers pulling up 60-80% it won't matter that much. Or if you are already a leader by long distance (Google, Microsoft and IBM earlier).