Hello, everyone!
I would like to let you know that my Internet is still dead...
However, I still managed to make some progress by writing code, which I will properly test when my Internet comes back. Another thing I did today was read through three chapters of the Typescript Handbook. Oh well, I need to do whatever I can despite this handicap and impediment!
Anyway, let's move on to my daily report...
Yesterday
I barely scraped by with whatever learning resources I had that worked off-line, namely my Scrum flashcards and the Typescript handbook.
Today
Here are the things I learned and worked on today:
Typescript
- I finished 3 chapters of the Typescript Handbook.
- reviewed about the common types in Typescript, and learned about the less frequently used ones like
bigintandsymbol. - learned about how Typescript narrows types, and different examples of doing so.
- discovered discriminated unions.
- read about the
nevertype and how it could be used for exhaustiveness checking. - learned about type predicate.
- understood why
unknownis better alternative toany, becauseunknownbecause its not legal to do anything with that value. - learned about overloading and case scenario in which it can be used.
Next.js
- coded my portfolio section and footer for the homepage.
- all this code wasn't tested properly because of lack of Internet, so that will have to wait.
Scrum
- I did some practice flashcards for Scrum.
- reviewed some of the things I've learned before.
I hope my Internet comes back soon...
Have a good day, everyone!
Resources/Recommended Readings
- Official Next.js tutorial
- The Typescript Handbook
- The 2020 Scrum Guide
- Mikhail Lapshin's Scrum Quizzes
DISCLAIMER
This is not a guide, it is just me sharing my experiences and learnings. This post only expresses my thoughts and opinions (based on my limited knowledge) and is in no way a substitute for actual references. If I ever make a mistake or if you disagree, I would appreciate corrections in the comments!
Other Media
Feel free to reach out to me in other media!
Top comments (4)
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.