Topic · 104 articles
TypeScript
Using the type system to make bad states unrepresentable.
TypeScript runs through almost everything I write, on the server and in the browser. These articles focus on using the type system as a design tool — modeling data so invalid states cannot compile — rather than as decoration bolted onto JavaScript.
The material spans backend and frontend, so it links naturally to the Node.js, NestJS, and React hubs.
Frequently asked questions
Do I need to know JavaScript before reading these TypeScript articles?
Yes. TypeScript is a superset of JavaScript, so the articles assume you can already read and write JavaScript and focus on what the type system adds on top — modeling data, catching bugs at compile time, and safer refactors.
Are these TypeScript articles about the frontend or the backend?
Both. TypeScript runs across the stack here — typing Node.js and NestJS services on the server and React components on the client — so the patterns apply wherever you write it.