The Developing Developer

 Feeling The Heat Here's what I'm up against. There are eight modules, total, in the JavaScript section of The Odin Project's curriculum. I'm almost half-way through the second module. Now, it is true that this is the longest module (with 11 sections compared to an average of 5 section per module), but it's still jarring to realize that I only have 13 weeks and 3 days until January 1st has its debut. It's a lot of work (and pressure!) to learn, build projects with new knowledge, and then feel somewhat prepared to interview in a fairly short amount of time. Ramping Up So what does this mean practically? The minimum, is that I'll need to spend more time coding. I've been pretty consistently working on coding for around four and a half hours a week. I'm trying to set a new goal of an average of one hour a day. Which should give me more like seven hours a week. I'm hoping to be able to work my way through the remainder of the JavaScript section with

 A Personal Code Library I'm currently in the middle of the first project in The Odin Project's JavaScript Course . One of the things that I've been realizing as I've built a handful of projects is that I can reference code I've written before. This gives me a starting point for solving novel, but similar, problems that existed in previous projects. Unlike college, self-plagiarism is encouraged in this industry because there's no good arguments for working from scratch on each and every new project you come across in the programming world. It would just be a waste of time and energy. So, like a bad college student and a good programmer, I copy and paste code from previous projects. One Big Problem? Another aspect of coding that has stuck out to me recently is the reality that a large project is just a the process of solving a handful (or a lot!) of small, interconnected problems. In other words, big problems are rather modular, and you build the different parts