What is the #100DaysOfCode challenge? It’s meant to be a challenge to complete 100 consecutive days learning to code and logging your progress on Twitter. I managed to hit 80 consecutive days before I missed my first day, and a day turned into three months. The challenge should really be called #100DaysOfTwitter. What can I say, life happens. Even during my break I was coding every day, it’s an essential part of my job, but daily I was practicing familiar concepts as opposed to learning and reskilling, I found #100DaysOfCode lent itself to greater rewards given the later. I found the best practice material was any project that forced me to really pour over the docs and grasp the fundamental concepts of how programming languages are used to build projects, also any course that covered a very broad or deep stack of new skills.
In my opinion these 100 day challenges teach you that any skill or habit can be learned. It’s all about building muscle memory. When doing something turns into second-nature the learning from it becomes almost a sure thing. It takes a substantial road block to stop the momentum you get from doing anything habitually for more than 40 days. For me the challenge derailed when I disabled Twitter notifications. It’s a noisy app, and I didn’t anticipate needing those triggers to remind me to make my daily contribution. I recently took the time to tidy up my Twitter account and now I rely much more heavily on the mute button. I’ve found that I’m using the app much less, but the algorithm actually does a very good job of serving me content I enjoy.
From this experience, my advice to people who take the #100DaysOfCode challenge is that it’s Ok to take a break, don’t quit or feel bad for yourself if you miss a day. If you take a break, I encourage you to complete the challenge on your own time, it’s rewarding to finish what you start and feel good about it – or don’t finish the challenge at all – still feel good about it. Ultimately you invested the time and energy for your own benefit, stick with those intentions. Completing this challenge or any other won’t define you. It’s about the lessons you can take along with you. I personally puttered through the last 20 days of the challenge over the course of 6 months, making my way toward what looked to be an uneventful ending until I came up with the idea to compose this summary and review blog post.