1) I was 30 years old. And in what many would consider a dream job. But I was pretty miserable. Because I knew I was letting my real dream--to become a screenwriter/filmmaker--die.

2) Sitting in my office one night, it hit me, if I did let the dream die, I would become toxic, because that's what death does, and that toxicity would ooze out of me, onto those I loved.
3)In that instant, I decided to make a shift, to find a way to finally, after years of denying it, do the thing. Try, at least. So I went to my best friend, @DavidLevien, who was already writing, and asked him for help.
4) David gave me The Artist's Way and said that when we had the right idea, he and I would write a screenplay together.
5) Soon thereafter, I had to good luck of walking into an illegal poker club in NYC, called David in the middle of the night, and we decided to write the thing.
6) we began outlining it, meeting whenever we could. And then, finally, on Columbus Day, 24 years ago today, we met at my office at work, because the company was closed for the holiday, and we started writing the actual script.
7) We wrote the first 10 pages that day, Oreos included, were off and running. Ever since, no matter what, we work on Columbus Day, together, this year, on video conference.
8) Whatever that creative thing is that you know you you're meant to do, but it scares you, do it, try. You don't have to quit your job. You don't have to tell the world. You just have to try, a little every day. And you can start on this day.

More from Life

“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. […]

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.