Domain Data Modeling using TypeScript Aliases, Brand Types and Value Objects
Tomasz Ducin
The reason we use TypeScript is so that it can catch inadvertant bugs you or your teammate will inevitable make whether that's passing the wrong prop to a component or assuming the data coming in is of a certain type (or there at all!).
Simply using TypeScript and it's primitive types isn't enough to stop sneaky bugs from pestering you.
e.g. you wouldn't treat an email and a user Id that are both strings the same way, even though TypeScript wouldn't differentiate the two.
As your project matures, you need a type system that will mature with it so you can be confident in the code you ship.
This course addresses your code from a data modeling perspective and gives you tools to incrementally build models that make sense for your application.
You can introduce each pattern step by step and maximize the benefits you get from them.
Credits
Maggie AppletonCourse Content
You might also like these resources:
Become familiar with the Workers CLI wrangler that we will use to bootstrap our Worker project. From there you'll understand how a Worker receives and returns requests/Responses. We will also build this serverless function locally for development and deploy it to a custom domain.
This is a practical project based look at building a working e-commerce store using modern tools and APIs. Excellent for a weekend side-project for your developer project portfolio
git is a critical component in the modern web developers tool box. This course is a solid introduction and goes beyond the basics with some more advanced git commands you are sure to find useful.