-
100-days-of-code
Fork this template for the 100 days journal - to keep yourself accountable (multiple languages available)
I got 46 days into the 100 days challenge, and for those 46 days, I kept a daily log in Notion of what I worked on each day (and then also posted it on Twitter each time). You can check that link to see exactly what I was recording each day, and feel free to copy for your own learning tracker! One of the especially useful elements of it for me was the "what I learned" box, where I tried to distill one key takeaway out of each day of learning. It doesn't have to be limited to 100 (or 30) days, of course, and you don't have to be participating in one of these challenges to just start your own similar log of what you learn each day. There's also an official GitHub repo for logging progress with 100 Days of Code; you can check out the forks to see some other examples of how people log their daily learning.
-
SurveyJS
JavaScript Form Builder with No-Code UI & Built-In JSON Schema Editor. Keep full control over the data you collect and tailor the form builder’s entire look and feel to your users’ needs. SurveyJS works with React, Angular, Vue 3, and is compatible with any backend or auth system. Learn more.
-
100-days-of-code
Fork this template for the 100 days journal - to keep yourself accountable (multiple languages available) (by Sazid99246)
I got 46 days into the 100 days challenge, and for those 46 days, I kept a daily log in Notion of what I worked on each day (and then also posted it on Twitter each time). You can check that link to see exactly what I was recording each day, and feel free to copy for your own learning tracker! One of the especially useful elements of it for me was the "what I learned" box, where I tried to distill one key takeaway out of each day of learning. It doesn't have to be limited to 100 (or 30) days, of course, and you don't have to be participating in one of these challenges to just start your own similar log of what you learn each day. There's also an official GitHub repo for logging progress with 100 Days of Code; you can check out the forks to see some other examples of how people log their daily learning.
-
learnInPublic
Inspired by Shuan Wang's learn in public, I decided to follow suite. These are my personal notes (by heyjiawei)
Another interesting option can be to write your notes as Markdown files in a public Git repo hosted on GitHub/GitLab/etc, like this person did. It can be nice to have it live in the same place as your code and means that folks like recruiters might see it when checking out your projects, and it doesn't disrupt your workflow as much if you spend most of your study time in a code editor (you can browse, write, and publish your notes all from within VS Code for instance).
-
The other big option is to post blogs or notes. It's pretty simple to start a blog right here on Dev.to, or on Hashnode, two blogging platforms specifically for coding. There's also a great community platform on Codedex.io where you can write blog posts, although you do need to complete a few lessons to "unlock" the community features. In these cases, there's already an audience and community on the site, so it's easier for your posts to get seen. If you want a more personalized blog, or want to blog about learning other stuff besides coding, you can try Substack. If you wanna get fancy, you can even self-host the similar blogging platform Ghost, like I do for my art blog! (Self-hosting is a great learning experience in and of itself!) IMO, these options are best when you want to write more focused and thought-out pieces like tutorials and guides, or even just "here's everything I know about CSS selectors" or whatever. Basically, I turn to these blogging platforms when I'm writing directly for the sake of informing other people.
