I’ve officially kicked off my learning journey, and my first topic of choice is TypeScript. Why? Because I wanted to dive deeper into modern JavaScript and understand why so many developers use TypeScript. Back in 2017, I started with JavaScript and hated it because there was no way to ensure type safety. But things have changed since then.
However, this week didn’t go exactly as planned. Due to lack of sleep and some personal challenges, I couldn’t always stick to my learning routine. But that’s part of the process – and despite the setbacks, I still learned a lot!
<h2>From Old JavaScript to Modern TypeScript – My Aha Moment</h2>
One of the most eye-opening parts of this week was understanding how JavaScript has evolved. I had heard about modern features before, but now I truly see why they were introduced and what problems they solve.
Here are some key takeaways that stood out to me:
🔹 Variables: var vs. let &amp; const
In the past, everything was declared with var, leading to unexpected issues due to hoisting and a lack of block-scoping. Today, let and const are the go-to choices because they prevent these problems.
🔹 Classes Instead of Prototypes
I had used class in JavaScript before but never questioned why they were added. The reason? Before ES6, JavaScript only had prototypes, which made object-oriented programming unnecessarily complex. TypeScript builds on this, adding even more structure and safety.
🔹 Arrow Functions (=&gt;) &amp; The this Problem
One of my biggest frustrations with JavaScript used to be that this didn’t always behave as expected inside functions. Arrow functions (() =&gt; {}) fix this by keeping this consistent—finally making my life easier!
🔹 Why TypeScript?
Modern JavaScript already introduced a lot of improvements, but TypeScript takes it a step further:
<ul>
<li>✅ Static typing helps catch errors early.</li>
<li>✅ Better code organization with interfaces &amp; enums.</li>
<li>✅ Improved developer experience with smarter autocomplete &amp; better tooling.</li>
</ul>
After this week, I finally understand why TypeScript is not just “nice to have” but a real game-changer, especially for larger projects.
<h2>Reflection &amp; What’s Next 🔥</h2>
I’ve realized that it’s okay if every day isn’t perfect – what matters is staying consistent. Even small progress adds up over time.
Next week, I want to apply what I’ve learned in a small TypeScript project. I’m curious to see what new challenges and insights will come up!
👉 How was your introduction to TypeScript or modern JavaScript? Were there any features that surprised you? Let’s discuss! 😊

Welcome to CodeBay, your premier destination for all things programming! This vibrant community is designed as an inclusive space where developers of all levels can share knowledge, collaborate, and grow together.

CodeBay - The Developer's Haven

The author shares their first week's experience learning TypeScript, highlighting key insights such as the benefits of variables like let and const over var, the advantages of classes, and how arrow functions solve the 'this' problem. They explain why TypeScript is a game-changer for large projects due to static typing, better code organization, and an improved developer experience. Despite personal challenges affecting their learning routine, the author stresses the importance of consistency and looks forward to applying their new knowledge in a project next week.

My TypeScript Journey – A Week of Insights 🚀

Currently working with Vanilla JavaScript, despite its obvious issues, I still have a lot of fun building stuff with it! But I also want to checkout TypeScript, see what the hype’s about 😄