About a year ago I made a promise to myself: spend an hour every day learning new stuff. In the weekends I would watch a course or read some articles but the time devoted on ‘learning’ was really inconsistent. That’s when a couple of months later I started my 100 days of code challenge.
You’ve probably seen this hashtag a couple of times but here’s a quick primer.
Code for at least an hour every day for the next 100 days. Make this a public commitment and track your progress.
Some personal extra rules:
logand update it each day.
logare pushed to GitHub.
It was this moment that I realized that these 100 days might be useful to force me to actually learn these concepts and start taking action.
That coding for an hour evolved around three main pillars:
This one is a bit obvious but I really felt it. You just have this solid goal at the end of each day that you have to complete this. I used Trello for daily tasks and just made a reminder task everyday.
When I first started I put some resources in the readme and thought that those kept me busy for at least 100 days. In the end I worked my way trough far more resources than originally thought. After almost 30 days I did all the resources I wanted to do when I started.
I couldn’t just read for a whole hour in a book I had to switch from time to time. Use different types of resources: read a book one week and watch a video course the other week. Switch it up.
The first week or two I just sat down for an hour straight but after I started noticing that I was more focussed by splitting up the time throughout the day. Maybe two sessions of 30 minutes or even three of 20 minutes. Mornings were pretty good for reading while the evening was more suited for video’s.
Look at your tracked time to get a grasp of how you’re progressing. Maybe the mornings you finish more resources than in the afternoon. It also gives you credibility, you can make the logged time public if you want to.