The following covers the unique aspects of TypeScript’s gradual typing, and how this can lead to types that are not accurate and can lead to bugs and runtime exceptions. We also cover ways to utilize the gradual feature of TypeScript to improve those types in an iterative fashion.
(more…)Author: JesterXL
-
JavaScript in 2037
I gave a talk at this years Richmond JavaScript Conference. I always wondered what would JavaScript look like then if many of the TC39 proposals were accepted. Given many take years, if I made the assumption by 2037, the few I wanted were approved, what would JavaScript look like then?
(more…) -
Front-End Staff+ Career Paths
Good video on front-end career path.
These guys have done some bangers on the nuance around AI for coders. Yes, their titles are click baity, but they have the intelligence, experience, communication skills to produce good content. Three things I want to point out they don’t cover in this video.
(more…) -
Error Handling for fetch in TypeScript
Introduction
The following post describes why and how you do error handling for
fetch.Why Care?
When you write code that does not handle errors, the code may break at runtime and when deployed to production. Getting PagerDuty calls at 3am are not fun, and are hard to debug because you’re sleepy. Doing error handling can both prevent those early morning PageDuty alerts, as well as ensure if they do occur, you have a better indication as to what went wrong, and if you need to act on it.
TypeScript can help you with types that make it more clear a piece of code can fail, and ensure you and other developers who build atop it months to years later also handle those errors. You just have to spend the time thinking about and writing the types.
(more…)