The replies under every engineer tweeting they've just been fired from Twitter are filled with newly verified and incredibly divorced men gloating the engineer will never work again, and tech leads from giant companies offering them jobs.
Andrew Lunny
@alunny
dachshund owner, frontend engineering at
Andrew Lunny’s Tweets
wait until he discovers the twitter codebase is full of WEAK references and LAZY vals, send tweet
1
47
Man I just have to be real for a second: what's happening at/to Twitter is making me deeply sad on multiple levels. I spent a lot of my formative years helping to build this thing, trying to do my little bit along with so many other great ppl to improve the code and the culture.
21
49
378
Show this thread
I've run the numbers and this is my best tweet.
Quote Tweet
The Loser
Despair
Fear and Trembling
Misery
If Hemingway Wrote JavaScript twitter.com/Twitter/status
7
5
Goodfellas (1990)
9
5
COWORKER: we need to find the root cause asap
ME: *takes long drag* the root cause is that our processes are not robust enough to prevent a person from making this mistake
COWORKER: amy please not right now
149
3,950
14K
sploot
4
Quote Tweet
Last month, @tylerkrupicka and I got to chat with @kyliebytes about the weekend we migrated Stripe's largest JS codebase from Flow to TypeScript. Very happy to see this article come out! businessinsider.com/stripe-migrate
Show this thread
1
4
6
We open-sourced the tooling we used for the migration–please reach out to us if you need help adapting it for your team 😀
Quote Tweet
I’m most excited about open-sourcing the tool we built to convert Flow to TS at scale, building on the work of @calebmer and Airtable. github.com/stripe-archive
Show this thread
5
Show this thread
Last month, and I got to chat with about the weekend we migrated Stripe's largest JS codebase from Flow to TypeScript. Very happy to see this article come out!
4
11
89
Show this thread
How do you transform millions of lines of flow into TypeScript? Join us this Friday with from to hear about their journey
1:48
227 views
1
4
7
I’m most excited about open-sourcing the tool we built to convert Flow to TS at scale, building on the work of and Airtable.
2
9
83
Show this thread
Over one weekend, my team at Stripe migrated our largest JavaScript codebase—containing 3.7 million lines of code—to TypeScript with minimal disruptions. Here’s how we did it:
29
307
1,657
Show this thread
Happy spot prawn season y’all
7
read image description
ALT
1
3
Show this thread
We work in North American timezones but Stripe has teams across the globe; I'm happy to redirect anyone who's interested.
7
3
78
Show this thread
Folks from under-represented groups are encouraged to apply; if you have any questions about the team or the role, my DMs are open.
3
4
79
Show this thread
My personal role was to go to meetings and ask "But could we do it sooner?" All the credit goes to the amazing team @partyfists and some other folks too smart to be on Twitter.
2
2
197
Show this thread
There are still several codebases to tackle, but this milestone puts the single biggest one behind us, and makes life better for hundred of our coworkers.
1
1
107
Show this thread
We're very fortunate to be in an organization that lets us take on gnarly problems and drive them to a solution, even as we had to shift focus a few times along the way.
1
2
153
Show this thread
End to end, it took us about a year from initial plans to shipping, including adding TS type definitions to our shared design system.
1
10
211
Show this thread
On Sunday we locked the repo, merged the change and… everything worked? (well okay, some things broke, but we fixed them quickly)
1
140
Show this thread
We knew we would want to lock the Stripe monorepo to merge such a huge change. Since we're a global company, the only feasible time was at the weekend, before our coworkers in Tokyo and Singapore would come online Monday morning.
4
1
115
Show this thread
And then the unenviable task of updating other dependencies–Jest, ESlint, webpack–to play nicely with the TypeScript code. And a lot of manual testing in QA to be safe.
2
104
Show this thread
We then took on the painstaking work of writing patch files, update code generators, and fixing new errors, while continuing to rebase and merge against the moving target of the Flow codebase.
2
1
95
Show this thread
Because of the size of our codebase, we had to introduce project references into a monolithic and entangled codebase, to keep tsc memory usage somewhat reasonable.
5
2
103
Show this thread
Why suppress errors? We want to improve the developer experience for Stripe engineers; the biggest win was to start using TS's superlative tools. Once the big jump to the new tooling was behind us, we could ramp up strictness, performance, coverage as needed.
3
8
172
Show this thread
Our biggest tweak was to run the codemod in two passes: once to generate ts{,x} files, and second time to auto-suppress errors.
1
3
134
Show this thread
4
29
432
Show this thread
Why? Flow had served us well since 2016, but TypeScript had clearly won over the frontend community, and the TS team has done a fantastic job with tooling and support. We want new developers at Stripe to write TS from day one.
3
12
417
Show this thread
Over the weekend, my team at converted the company's largest JS codebase from Flow to . We modified about 3.5 million lines of code, and then hundreds of developers came in Monday morning ready to write TS.
102
671
6,388
Show this thread
How to make caramelized onions:
* it’s too late, you should have started an hour ago
3
38
read image description
ALT
4
Me watching Old:
When are they gonna get old?
1
2
me writing my self-review
1
8