1/ Thread: "A Silicon Valley Ponzi Scheme"
Thanks to @chamath for laying this out in Social Capital's 2018 annual letter.
I've always appreciated his outspokenness.
This is creating a big bill that will soon come due...
But it's not who you think (that does), and the dynamics we’ve entered is in many ways creating a dangerous, high stakes Ponzi scheme.
Someone has to pay for the outrageous costs of this style of growth. Will it be VCs?
Likely not.
Eg: VCs habitually invest in one another’s companies during later rounds, bidding up rounds to valuations that allow for generous markups on their funds' performance.
if you’re a VC with a $200 million dollar fund, you’re able to draw $4million each year in fees.
Most funds never return enough profit for managers to see a dime of carried interest.
If u can show marked up paper returns & then parlay those returns into a newer, larger fund—say $500 million—you now have a fresh $10 million a year to use as you see fit.
There’s some deep misalignment here...
Partly why American healthcare is so expensive is bcos insurers, who play a key middleman role in setting prices for medical care, have a 2-sided biz model:
High costs allow them to charge higher premiums, allowing them to pull steadily more and more money out of patients’ and payers’ pockets.
In the end, both, patients and payers are the ones who end up as bag holders footing the bill.
The same thing is happening in today’s venture world.
Just as insurers’ biz model translates to higher costs of patient care,
So if its not VCs, who ends up holding the bag?
It’s still not who you’d expect.
In some cases, high prices may even work to their advantage.
Unlike the other pass-the-buck schemes
The real bill ends up getting shuffled outta sight to 2 other groups.
The 1st as u may guess are early stage funds’ limited partners, particularly future limited partners investing into the next fund.
Marking up Fund IV to raise money for more mgmt fees out of Fund V is so effective bcos fundraising can happen much faster than the long & difficult job of building businesses & creating real enterprise value
The second group of people left holding the bag is far more tragic: the employees at startups.
Although originally helpful as a way to incentivize and reward employees for working hard for an uncertain outcome,
Overall, you can understand how this arrangement endures:
Those companies then go spend the money on more user growth, often in zero-sum competition w/ one another.
What is the antidote here? Its 2-fold.
The 2nd is to break away from the MLM scheme that the VC-LP-user growth game has become.
It’s time to wait patiently, as the air is slowly let out of this bizarre Ponzi balloon created by the venture capital industry.
More from Tech
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.