Falling Behind

Creating the Timeline

I finally crunched the numbers and I'm falling far behind on my deadline. I'd like to wrap up The Odin Project's JavaScript Course by December 18th (so that I have time to do some interview prep before I'm applying for jobs come January). Right now, I'm working on material that I should have wrapped up the week of September 19th. That puts me about 3 weeks behind on my 16 week (as of the beginning of September) schedule. It does not feel good to be that far behind. I'm hoping to log a lot more hours over the next few weeks to catch up and be "on schedule."

Logging More Hours

Over the last two weeks I've averaged 6 hours and 45 minutes a week. Pretty close to my hope of a 7 hour a week average! I've been able to cover more ground, but I'm also recognizing that spending time on the various projects can take up a week or so of my time. I'm considering dividing my time between projects and working through the articles assigned past the current project to help me to make more progress. Part of covering more ground is sinking more hours into learning how to code, and the other part is being smart with my time and making sure I'm able to have focused, dedicated time when I'm working on coding so I can make sure time spent "coding" is actually time I'm spending programming (or learning).

Goodbye Weekends?

Something I'm recognizing is that I'm hardly spending any time coding/learning on the weekends. I'm thinking it may be wise to try and focus a bit more on my weekends to log more hours to catch up on the timeline I'm wanting to align with. Yes, I've got to catch up on chores like everybody else, but I may be able to set up a bit more time management to accomplish more coding during the weekend.

What Am I Learning?

I've been working through both JavaScript Classes and Webpack. JavaScript Classes are a bit of a controversy, but they are a specific way to allow inheritance to be passed down to child objects. Webpack is a powerful tool that I've only scratched the surface of. It's a powerful way to automate downloading dependencies, dynamically refresh a page, and a billion other things. I'm looking forward to getting a little more comfortable with Webpack as I've been looking forward to the more powerful automation tools out there in the developer world. Let's hope I can take this all in and figure out how to implement it in my upcoming project!


Tim David

Comments

Post a Comment

Popular posts from this blog

Confronting Busyness

 Accepting Busyness I've been able to up the hours I'm putting into coding. I've been surpassing 6 hours a week pretty consistently. I'm proud to nearly double what I was putting in before. However, my hope to code on the weekends continues to be unrealized. The realities of being a responsible adult keep catching up with me on the weekend and coding keeps getting dropped in the juggling act. And that's okay. My goal is ambitious, but my current job is flexible. If I need another month (or two) before I've got the skills needed to land a job I'm really wanting, they will work with me. I'm really glad to have that kind of buffer, especially now that learning everything come January looks less and less realistic every week that goes by. Streamlining Processes I'm getting better at recognizing when I've hit a wall and then changing my approach to break through that wall. I'm in the midst of building a to do list web app and there's a lot of
Read more

My Coding Journey: Part 2

 The Pivot Sometimes you have your head down for a long time and you really need to come up for air. That's what I realized in April. I was on this fairly straightforward path of becoming a web developer (see the previous post) but I had committed to this path before I understood programming enough to consider a variety of options. I decided to take a short break and come up for air, smell the roses, and talk to people. I started talking to friends and friends-of-friends who are currently working in tech. I asked them how they got into tech and if they had any advice for a self-taught programmer. This was very helpful at this stage since I had been programming for a few months now and could actually understand a lot of the jargon my friends ended up throwing around. And this gave me some perspective. The Perspective Being able to talk to friends in the tech industry was super helpful and I also returned to YouTube for a few hours (not all at once). I had come to this realization wh
Read more

My Coding Journey: Part 1

 The Decision Any good story has an interesting beginning, and I like to think my story does. I had just graduated from Colorado State University with my B.S. in Psychology. I applied for jobs left, right, and center (I'm looking at you Indeed). I ended up getting a few offers, but nothing I actually wanted to do--either the pay was to low or I could clean carpets, so no thanks. I decided I was done with school and I wanted to find something that would pay well and also be interesting to do. I ended up landing on learning to code as I considered my various options. I have been a little bit of a tech hobbyist--trying different Linux distros, following the latest devices in tech, that kind of thing. So I decided to give it a low-stakes investigation. After all, if I hated it, I could just dip and then figure something else out instead. The Path I ended up watching a lot of YouTube videos to figure out how the hecking hey to teach yourself how to tell dumb computers to do smart things
Read more