Then over the decades information asymmetry started to chip away at this with investors realizing they really only needed to keep the founder happy, and they could steadily chip away at the outcomes for the rank and file given those young engineers would keep coming in based on the mythology of getting rich from the previous generation.
It took awhile, but now that trust has been fully eroded, and simultaneously FAANG have recognized the value of top engineering talent, paying salaries to ICs that would have been unthinkable in the 20th century.
It's going to be very difficult for investors to win back trust because now the information asymmetry works the other way, with young talent just assuming ISOs are worth nothing. Even if founders make an effort to do right by early employees, it's very difficult to demonstrate this to someone who is suspicious but not seasoned enough to know what questions to ask.
I'm not saying you're wrong at all -- most typical startup ISO offerings suck and are not good situations for employees. That said, as a founder who custom designed our stock plan to be as employee-friendly as we could, there is a better way when actually done right and not just "following the standards".
Stock plan improvements like super long post-termination exercise, offering RSAs instead of just stock options, and most importantly in my opinion, adequately educating your employees on the risks and return possibilities of their equity!
While many employees' eyes will glaze over a bit if you start citing tax code, helping them get the basics and fully internalize the risk/reward tradeoff is both doable and necessary!
I've seen far more shit habits from habitual startup employees than those who come from Big N. The people who come from big public companies are almost always better at best practices and writing code than startup employees. I don't believe working at startups really gives you good sense for architecture, scalability, readability, or a variety of aspects of programming. It's almost all about getting that short term dollar to get to the next stage of funding. So, raw first time implementation speed gets prioritized over all other aspects. I don't find many startups have very strong technical voices either. CTOs frequently being product people in disguise, etc. That's my experience...
At a functioning startup if you overbuild you die. Everybody working at one knows this so people are much more pragmatic.
At a large company, your over engineered crap is lost in the noise.
The "sense of legitimate urgency" is a bunch of bullshit. It's just as made up as it is at any other company. I've worked at startups from seed stage to unicorn and a lot of the real urgent things aren't things that engineering needs to do - it's other shit and usually has to do with partnering with someone. And that usually isn't an engineering problem. Engineering is rarely the blocker for things being rolled out. It's usually that product can't determine what the right product is - business can't get the partners they need - etc.
At a small company - your overengineered crap becomes the institutional bullshit that holds the rest of engineering back for years because no one can replace it because there's no time for refactoring. At least at a big company you can throw away those solutions that don't work for people. At a small company - it becomes the shit that holds you back from doing things efficiently for years.
Consider that it makes no sense to do almost any job if you can work as a dev at a FAANG.
Not everyone can work at a FAANG, moreover, this is not just a VC/Founder vs staff problem, it's an existential startup problem vis-a-vis FAANG and the rest of the world. You see the issue in housing affordability etc..
That horse has bolted the barn long ago.