Table of contents
No headings in the article.
Over the weekend I decided I'm going to start making writing part of my daily habits. As an avid technical blog consumer, I had sort of a "gotcha" moment when I finally realized in a way I was hindering my personal development by not writing about the things I was learning. I found myself having to re-look up a blog I had previously read or go back to the documentation to re-look something up that I previously knew how to do. In many cases, this is normal. You can't remember everything you learn all the time. However, writing about it can increase your chances of having that knowledge stick long term.
For the longest time, I've been such a huge fan of Kent C. Dodds, and one thing he said a long time ago in one of his talks that has always seemed to resonate with me was the "Consume, build, teach" approach. Consume the content, build something with it, then teach it to someone else. This helps reinforce what you've learned. This blogging habit is going to be one way of me teaching what I've consumed and built. The driving factor in me starting this was to level up my skills and knowledge to become the best possible frontend engineer I can be, while also retaining as much knowledge as possible.
I would be doing myself a disservice if I didn't mention Tiger Abrodi in my first blog post, who is also another member of the engineering community and was also a driving factor in my blogging journey. Thank you for the motivation 🔥
Did you find this article valuable?
Support Jordan Long by becoming a sponsor. Any amount is appreciated!