1/ There is so much idol worship in Silicon Valley re: successful founders and investors. But there is a common denominator for success which is rarely addressed: Privilege

I want to confess my own journey of success, as it relates to Privilege.

2/ My Korean parents were poor when they arrived to the US, seeking opportunities for their future kids. Upon immigrating, my father Germanized the spelling of our last name (B-A-H-N), with the rational that a white-sounding last name would open up opportunities. I think it has.
3/ By the time I was born, my parents were doing very well. I never suffered their trauma of poverty. I lived in a big house and went to the best public schools. As a kid, I never felt like I was missing any resources.
4/ Partly because of my abundant resources, I was able to attend Stanford. Mom and Dad paid for that too, and I graduated with no debt. They even bought me a Honda after completing grad school! (I know, spoiled brat)
5/ With my family safety net, great education, zero debt, economy car, and abundance mindset--I went forth into the world ready to take huge risks. Taking risks was easy and natural, because I COULD AFFORD IT. Success followed.
6/ I’m not saying that I didn’t work hard throughout my journey; but Privilege was like a tailwind that seemed to accelerate my career.

So why raise the issue of Privilege?
7/ In Silicon Valley, Privilege seems more normal/common than not. It feels like so many founders/investors here aren’t running the same race as regular people. If this were a 100-meter dash, we got a 40-meter head start while everyone else waits at the starting line.
8/ Our team @HustleFundVC believes great founders look like anyone and come from anywhere--privileged or not. I’m starting to realize that Privilege should be an important factor in the assessment of founders.
9/ By better understanding a founder’s personal journey, we should use that knowledge to tare how far along privileged/unprivileged founders should perform across an equal timeline.
10/ Founders with a lot of resources will naturally report more progress than founders who have very little resources, over the same period of time. Both still could be equally great in outcome over the long term.
11/ I’m still thinking a lot about how to approach Privilege in Silicon Valley. As a starting point, I wish more people here would recognize it when discussing their ‘self-made’ success.

PS: big props to those founders/investors who have made it without Privilege.

More from Eric

You May Also Like

And here they are...


Remember, this money is just fun. If you launched a product (or even attempted a launch) - you did something worth MUCH more than $1,000.


The winners 👇


Lattes For Change - Skip a latte and save a life.

@frantzfries built a platform where you can see how skipping your morning latte could do for the world.

A great product for a great cause.

Congrats Chris on winning $250!


Instaland - Create amazing landing pages for your followers.

A team project! @bpmct and @BaileyPumfleet built a tool for social media influencers to create simple "swipe up" landing pages for followers.

Really impressive for 24 hours. Congrats!


SayHenlo - Chat without distractions

Built by @DaltonEdwards, it's a platform for combatting conversation overload. This product was also coded exclusively from an iPad 😲

Dalton is a beast. I'm so excited he placed in the top 10.


CoderStory - Learn to code from developers across the globe!

Built by @jesswallaceuk, the project is focused on highlighting the experience of developers and people learning to code.

I wish this existed when I learned to code! Congrats on $250!!
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

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

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.