Archive

Well, I forgot to send out an email in 2020. Oops... 🙇

Anyway, it's been an interesting way to start the year for sure. Back in October, I started writing course on TypeScript & React. I wanted to write a guide to take the layperson who might just be getting started with coding (maybe a career transition) and senior devs who are trying to onboard themselves to these technologies. 35,000 words later, several people begged me to stop, I mean, they asked me to share what I wrote with people!

That's where typescript.wtf came from and I want to hear from you. What's the biggest pain point you've had with TypeScript or React? Reply to this email and let me know, I'll break it down and write up a solution.

I've had some of my favorite dev friends share with me some theirs and broke down their issues over on that site.

One the first things you're going to encounter working with TypeScript is this idea that it's prohibitive or it's a lot of setup. I've been there. Then I remember this quote:

TypeScript shines not on day 1, but on on day 100, and becomes a freaking supernova on day 500. -- Jared Palmer

As you start working in a codebase you don't have a lot there. Then add some community types for the libraries you're using; that's one level of productivity, the libraries you're using are now showing where you're using their API wrongly, and that's sort of helpful on a level but we can do better.

Then you have more code and more requirements in your project and those types you're adding accrue by a magnitude. At this point your application has certain models or pieces of UI or concepts that you want to make discernible, like in a chat app you might have a type interface for the message and one for the thread of messages.