The Good, the Bad, and the Action
Reflections for the Halfway Mark of #100DaysOfCode
Finally, I decided to participate mid-March and was enthusiastic about it. I was going to code/design/research every day and my real life job (I work in retail) wasn’t going to interfere.
How wrong I was.
I started skipping days because retail and low spoons didn’t allow for learning. I allowed myself leeway and changed my already modified rules. Once I pledged that I would spend non-retail days working on #100DaysOfCode, I found myself anticipating each day I could work on something.
At the beginning, I had goals in my mind but didn’t vocalize what they were. To be honest, I can’t recall what those goals were. In the meantime, I’ve noticed trends in my learning path.
- With the courses I took, there was a product created by the end. These projects populate my portfolio showcase. Unfortunately, that means there aren’t any projects that aren’t course related.
- At the beginning, I wanted to do an equal amount of coding and design work. I believe I only have a handful of days committed to design work. Along those lines, I didn’t read nearly the number of tech books I wanted to.
I need to build projects outside of coursework.
Rick West wrote a great post about getting yourself out of a coding tutorial rut. He argues that you’re not really learning anything if you’re just copying what the instructor is doing. Also, you don’t go through the process of thinking through what problems there are and what the solutions could be.
I need to make my designs a reality instead of keeping it in a notebook.
I like to call myself a designer, but I admittedly can’t allow myself to post anything. I have to remember that everyone starts somewhere and my designs can “suck” as long as I learn from what I’ve done in the past.
Here’s to the next 50 days!