100 Days Commitment
The first two times I started the #100DaysOfCode challenge, I jumped in head-first without a plan and the public commitment on Twitter wasn't enough to help me get over the shame I felt for falling off.
This time, I'm armed to the teeth with plans and contingency measures and multiple platforms for accountability. And I'll be honest, I'm still a little scared that I'll fall off like the last two times. But I read somewhere that bravery isn't the absence of fear, rather it is acting even though there is fear. So this is me, doing it scared, on my third attempt at this challenge. I hope someone who's been putting it off like I had will be encouraged by this to make a plan.
Okay, on to the juicy stuff: scope and rules. Success is your ability to properly assess your failures and learn from them. From assessing my previous attempts and reading other people's accounts of their own attempts, I noticed that a common mistake is setting unrealistic expectations that seem small in the moment but very quickly pile up. I'm sticking to a small scope and simple rules.
The 100DaysOfCode's first rule is to code a minimum of 1 hour a day. I hope to get an average of 4 hours daily, however the goal is 1 hour. This way I can avoid burnout and the shame that accompanies not accomplishing what you set out to do.
The second rule is to tweet every your progress every day. I'm interpreting this rule to be 'publicly announce your daily progress so you can stay accountable'. I don't see myself being consistent with Twitter logs so instead I will be doing my daily logs in the 100DaysOfCode channels on two discord servers I'm on. Doing this in a smaller community of people who are also on the same journey will be easier for me to commit to. I'll post updates on LinkedIn every 10 days though and I'll link my GitHub log repo so my progress will be trackable here.
I have 3 projects I will be working on during this challenge, in order of priority: a playlist webapp, a utility functions npm package, and a bingo webapp. My goal is to complete the first app, the other projects are there because I often need to work on multiple things at once to offset the effects monotony has on my brain.
I want this project to showcase my current skillset as none of my existing projects do. I'm taking all the advice I've read and heard about being job ready and I'm putting them to practice in the following 100 days. I hope you'll follow along with me on this journey.
This has been a rather lengthy post, thank you for reading thus far. I'm looking forward to this challenge and the better developer I'll be at the end of it.
#100DaysOfCode #100DaysOfCodeChallenge
