After ten years, I am leaving Facebook.
I am starting a company.
It has been an incredible experience for which I am grateful.
I will also be investing more in startups as opportunities arise, and investing in open source projects/communities including @reactjs related technologies, @reasonml, UI frameworks, programming languages.
Thank you everyone for the outpouring of encouragement and gratitude. I assure you that out of everyone, I have gotten the most from of this journey. An incredible - no unbelievable - story so far. A new chapter begins. One paragraph at a time.

• • •

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

Keep Current with jordwalke

jordwalke 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 @jordwalke

27 Nov 18
npm package malware is also a technology problem. Deps should be built at install time, on-host from original inspectable sources but npm practice is to build at package publish time so it runs everywhere w/out a build step. How badly you want JS to "not" be a compiled language!
So you have everyone turning their "JS" into *actual* JavaScript in a way that obscures the original intent, allowing things like the recent vulnerability to slip in easily. To fix this you need a completely different package management philosophy centered around.. Builds!
You can't easily take existing npm packages and run their publish steps at install time on your host, for many many reasons - these transpilation/minification toolchains are huge because they *could* be - they were just publish time dependencies that were dropped once published.
Read 7 tweets
19 Jul 18
Hot take: Single page documentation is superior to documentation that spoon feeds three paragraphs at a time to you with prev/next pagers at the bottom.
1. Use command+f to search for things like you always do.
2. Easier to keyboard navigate.
3. Can still hyperlink to headers...
4. Instantly gives you all of the docs "offline". Just keep a browser tab open or save the HTML or print to pdf.
5. From maintainer's standpoint, no need to sign up for some service that you (might have to) pay to index your search.
6. Search works in offline mode too because you don't need to connect to a service.
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

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

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!