#100DaysOfCode Parts I and II
When I was starting out I did two stints of #100DaysOfCode which is as the hashtag reads a commitment to work 100 consecutive days on coding. I thought that if I did these it would help me buckle down and work on learning to code and for those days it kind of did, but after the stints I remember feeling kind of burnt out.
As I hype myself up right now to go back and work on Python and getting back into working with this language, as well as, prepping to take the Certified Entry-Level Python Programmer certification (PCEP) – [ I really just want to feel kind of validate in my learning, which is the reasoning behind the exam for me] – I find myself thinking back at these stints of daily coding and what might have gone wrong for me.
Although, I am the kind of person who is good with making and sticking with commitments and structured work/learning, I am also the kind of person who is easily annoyed by monotony. The problem for me with #100DaysOfCode is that day after day it can get monotonous and make people such as myself not want to do the work. This is a personal issue and probably an issue with the way in which I went about doing the challenge. I think that instead of focusing on one book for weeks or one project I should have had concurrent projects which I could have rotated when one go stale.
If I decide to do this challenge again this I think that I will have a few projects going and also have FreeCodeCamp rework / Github Clean up interwoven. I’m still on the fence with whether or not I should do something like this challenge, but some parts of it were very good for me, it made me productive in a way.
“The critical ingredient is getting off your butt and doing something. It’s as simple as that. A lot of people have ideas, but there are few who decide to do something about them now. Not tomorrow. Not next week. But today.”
~ Nolan Bushnel
Build A Security Ninja 