Share this page!

swyx 🦄 Profile picture
Twitter logo
Jul 10, 2020 • 6 tweets • 2 min read
💁‍♂️ How to Play Long Term Games:

Systems > Goals
Discipline > Motivation
Trust > Distrust
Principles > Tactics
Writing > Reading
Vulnerability > Confidence
North Stars > Low Hanging Fruit
Trends > News
Habits > Sprints
Questions > Answers
Problems > Solutions
People > Projects
Listening > Arguing
Empathy > Enmity
Values > Metrics
Actions > Reactions
Health > Wealth
Forgiveness > Revenge
Automation > Decision
Delegation > Control
Growth > Fixed mindset
"Yes, and" > "Well, actually"
Community > Solo effort
Identity > Outcomes
Science > Social Science
Integrity > Capability (h/t @chamath)
Designing > Forecasting
History > Geography
Micro > Macro econ.
Resilience > Perfection
Redundancy > Efficiency
Lasting > Winning
Wisdom > Intelligence
Drive > Inspiration
Investing > Spending
Proactive > Reactive
Data Structures > Algorithms
Audiobooks > Podcasts
Movies > TV
Boardgames > Computer games
Wearables > VR
Email > Slack
DM > Subtweet
Textbooks > Google
Courses > YouTube
Threads > Memes
Magazines > Newspapers
Theme songs > Soundtracks
Slogans > Billboards
Wikis > Q&A
Personal Blog > Medium
Reviews > Silence
Morgan strikes a nerve here with "Permanent skills":

- Don’t be a jerk
- Change strongly held views
- Get along w/ disagreement
- Get to the point
- Get out of the way
- Accepting hassle when needed
- Distinguish "out of favor" from "wrong"

ImageImage
Be too busy to "do coffee"

Too busy for gossip or grudges.
Too busy for dishonesty or drama.
Too busy for rage or regret.
Too busy for jealousy or judgement.

Be too busy for things that don't matter.
So you can be INSTANTLY available for things that do.

• • •

Missing some Tweet in this thread? You can try to force a refresh
　

Keep Current with swyx 🦄

swyx 🦄 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @swyx

swyx 🦄 Profile picture
Feb 17
One of the most insane proof points of developer product-market fit is when companies start *listing your tech* on JD's to appeal to engineers.

So we started a job board for our users 1 year ago.

👩🏼‍💻 Here's a sampling of @temporalio jobs and people you can talk to about them: jd's that feature temporal
💳 Stripe

@thisdrewhoskins from the @StripeDev Workflow Engine team even gave a talk at the @temporalio meetup! (temporal.io/stripe)

Build the infrastructure behind the behemoth growing the GDP of the Internet:
stripe.com/jobs/listing/i…
⚡ Bolt

If you're picking up what @theryanking is putting down, you can join @bolt to solve one click checkout for everyone.

Talk to @roopakv who has an encyclopedic knowledge of the best devtools in the industry, and runs temporal.works!

JD: bolt.com/careers/softwa…
Read 5 tweets
swyx 🦄 Profile picture
Feb 13
Shreyas is doing a live workshop for super-followers now, he gave us permission to tweet notes and it's been a hot minute since I livetweeted an event, so here goes:

Extended annotations on @shreyas' Time Management 👇🏼
There are 3 levels to product work:

1 - Execution (Getting Things Done - Outputs)

2 - Impact (Being Effective - Outcomes)

3 - Optics (Getting Recognized - Perception)

Everybody has different stack ranked/default levels.

If you are optimizing for Optics, you should not do Radical Delegation () - bc other people will get credit for work that you did behind the scenes.

(in chat: ignoring optics sounds nice until you run into someone who is really, really good at optics)
Read 14 tweets
swyx 🦄 Profile picture
Dec 27, 2021
In 1976, Stuart Feldman made Make, the build system that secretly runs ~all open source.

In 2021, @jaredpalmer spent the year working on a new tool that is up to 85% faster. @Vercel snapped it up last month.

Why @TurboRepo will blow up in 2022:

dev.to/swyx/why-turbo…
The origin story starts with this looongstanding open issue on TSDX from @n_moore. As an early helper on TSDX I shied away from it bc I thought that it should be solved by dedicated tooling like @yarnpkg.

Jared went one step further and *built it*.

Big monorepo shops like Facebook and Google have loads of tooling to make monorepos work, but this class of tooling never made it out into open source.

@TurboRepo does 3 things:
- Make monorepos zero config
- Make monorepos incrementally adoptable
- Make monorepos scale
Read 11 tweets
swyx 🦄 Profile picture
Oct 31, 2021
Trying out @factoriogame for the first time this weekend

If you don't hear from me... you'll know its going well screenshot of factorio game
@factoriogame streaming it actually DM to jump on stream and chat if we know each other
Before I attempt the last tutorial I'm checking out a few tips and tricks videos to see what I'm doing suboptimally and there's a LOT! man, tutorial was good but I was doing so much manually that they could've just told me outright...

this is the best one
Read 4 tweets
swyx 🦄 Profile picture
Oct 12, 2021
This year I've done a total 180 on open source strategy.

Remember Elastic making a fuss with "Amazon: NOT OK"? I was quite persuaded. If MongoDB, Redis, Cockroach, Confluent relicensed and do fine, maybe SSPL just becomes acceptable "open source".

Now I think MIT is just fine.
Probably my biggest test of confidence was in March when @martin_casado and @davidu pushed back on the open source religion - if your monetization is SaaS, then open source is just marketing (there's nuance here, pls read his replies before reacting)

Open sourcing has a cost - at @temporalio it impacts decisionmaking in engineering, product, docs, devrel. Tradeoffs we wouldn't have if we just had a free tier.

But look at how extensively @NetflixEng has been able to adapt our SDKs and devtools:
Read 12 tweets
swyx 🦄 Profile picture
Sep 11, 2021
Never thought I would see a frontend eng team celebrate shipping a static marketing site with 847kb of JS.

Until I saw what it used to be…

notion.so/blog/migrating…
I'm no perf expert or perf shamer (let he who is without sin...)

But here's what I do believe:

1. local Lighthouse runs are not credible. Use webpagetest or web.dev/measure.

2. you do NOT have to use the same tech for app and site! :)
in fact i’m -so- not a perfshamer I shall now say the thing I’m not supposed to say:

before today you didnt know or care that Notion had a 9.1MB JS marketing site; if it impacted them enough they would’ve fixed it sooner; you may have a fast site but they have 10 million users.
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

Like this author's thread?

Get emails when @swyx has new unrolls!

Check out other threads from @swyx!

Read all threads by @swyx

:(