π Day 2 of my 30 Days of Learning Challenge
Next day's focus was all about TypeScript, and it opened up a new way of thinking about code for me. Iβve always been comfortable with JavaScript, but this statically typed superset challenged me in a good way.
We started by covering the basics β type annotations for variables, function parameters, and return values. Then we moved into more advanced concepts like interfaces, type aliases, and optional vs required properties. It felt a little rigid at first, especially coming from JavaScript's flexibility, but the benefits quickly became clear.
I built a simple to-do app and used TypeScript to define the shape of each task, enforce valid input, and handle errors gracefully. By the end, my IDE was catching mistakes before I even ran the code β something JS never gave me. That sense of confidence and clarity was super motivating.
One thing that stuck with me: βTypeScript makes you design your data before writing the code.β That discipline made my logic cleaner and more reusable. It also made debugging easier because everything was more predictable.
I can already tell that TypeScript will be central to how I build both backend and frontend features going forward β and Iβm actually excited about that.
π¬ Question for Readers:
How has using TypeScript changed the way you think about writing JavaScript? Did it help you avoid bugs, or did the strict typing feel like a barrier at first?
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.