Daily Bookmarks to GAVNet 02/20/2021

More from GAVNet

More from For later read

How I created content in 2020

A thread...

Back in Aug 2016, I started creating content to share my experiences as an entrepreneur.
Over 3 years I had put out 1,200+ hours of content - posting every week without


Little did I know that something I started almost 4 years back would give my life an entirely new direction.

At the end of 2019, my biggest platform was LinkedIn with ~700K followers.

In Jan 2020, I decided to build a team that would help me with the content.

I ran a month long recruitment drive to hire a team of interns.

It comprised 4 detailed rounds - starting with my loved 20 questions, then an assignment, then a WhatsApp video round and finally F2F.

Through 1,200+ applications, I finally selected 6 profiles, starting March.

I am a firm believer in @peterthiel's one task, one person philosophy
So the team was structured such that everyone was responsible for ONLY one task

1. Content ideas
2. Videography
3. Video editing
4. LinkedIn (+TikTok) distribution
5. FB+IG distribution
6. YouTube distribution

You May Also Like

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.
“We don’t negotiate salaries” is a negotiation tactic.

Always. No, your company is not an exception.

A tactic I don’t appreciate at all because of how unfairly it penalizes low-leverage, junior employees, and those loyal enough not to question it, but that’s negotiation for you after all. Weaponized information asymmetry.

Listen to Aditya


And by the way, you should never be worried that an offer would be withdrawn if you politely negotiate.

I have seen this happen *extremely* rarely, mostly to women, and anyway is a giant red flag. It suggests you probably didn’t want to work there.

You wish there was no negotiating so it would all be more fair? I feel you, but it’s not happening.

Instead, negotiate hard, use your privilege, and then go and share numbers with your underrepresented and underpaid colleagues. […]