I respect your dedication to read the Typescript handbook... In my (limited) experience, coding books are really hard to chew through without exercises to work on alongside them.
I think I prefer projects over reading books and documentations as well, because it engages my brain more. I enjoy dealing with errors and learning from my mistakes, as frustrating as those are.
However, reading documentation and books also enable you to encounter concepts that you will not stumble upon if you just coded on your own.
Typescript is pretty nice because of the safety and clarity it provides, especially in a team setting with a large codebase. It's definitely worth learning. However it's not perfect and has its downsides so I wouldn't always use it on any project over JavaScript.
I definitely agree that reading documentation and books lets you encounter concepts you wouldn't otherwise see. There's some ideas that you wouldn't even think of trying to find. One of my previous mentors said that Google can only help you figure out what you know that you don't know.
It's cool to hear about Typescript; I'm new to the JS space entirely, so I knew nothing about it. After reading your post yesterday, I did a little research on Typescript and I saw that its strong typing makes code a lot more rigorous. It makes sense then that it would be beneficial in large codebases.
Also, the more I learn about React the more I hear about Redux. Namely that it is a lot to learn, but that it is very useful for maintaining state once you do learn it. It seems that getting into Typescript just for Redux is probably worth the time.
I respect your dedication to read the Typescript handbook... In my (limited) experience, coding books are really hard to chew through without exercises to work on alongside them.
How are you liking Typescript so far?
Thank you for the kind words!
I think I prefer projects over reading books and documentations as well, because it engages my brain more. I enjoy dealing with errors and learning from my mistakes, as frustrating as those are.
However, reading documentation and books also enable you to encounter concepts that you will not stumble upon if you just coded on your own.
Typescript is pretty nice because of the safety and clarity it provides, especially in a team setting with a large codebase. It's definitely worth learning. However it's not perfect and has its downsides so I wouldn't always use it on any project over JavaScript.
I definitely agree that reading documentation and books lets you encounter concepts you wouldn't otherwise see. There's some ideas that you wouldn't even think of trying to find. One of my previous mentors said that Google can only help you figure out what you know that you don't know.
It's cool to hear about Typescript; I'm new to the JS space entirely, so I knew nothing about it. After reading your post yesterday, I did a little research on Typescript and I saw that its strong typing makes code a lot more rigorous. It makes sense then that it would be beneficial in large codebases.
Also, the more I learn about React the more I hear about Redux. Namely that it is a lot to learn, but that it is very useful for maintaining state once you do learn it. It seems that getting into Typescript just for Redux is probably worth the time.
Thanks for the posts, I learn a lot :)
If you're going to learn Redux, make sure to learn the modern Redux Toolkit. Old Redux is kind of not worth it anymore.