My First 100 Days of Code

Home / Technology / Web Development / My First 100 Days of Code
I'm wrapping up my first round of 100 Days of Code, making plans for my next, and catching up on some long-overdue tasks.

Oh, hello! Long time, no see, eh? Sorry about the extremely late update. I planned on posting a big ‘100 Days of Code’ update/review earlier this week, but got caught up doing a few other things. I’ll explain all that in a bit, but first…

I Finished The 100 Days of Code Challenge!

As you probably already know by now, last Saturday was DAY 100 of first round of this challenge. If you recall, in my last update, I explained that I probably wasn’t going to post until after the challenge was over because there were two projects left to do and I really wanted to finish.

Sadly, I did not finish the last project. I got started on the UI but didn’t have enough time to complete the project.

Project #4 : JavaScript & React.js Calculator

The good news is that I DID finish one of the projects and now have a fully working, functional, lovely JavaScript & React.js calculator.

[codepen_embed height=”500″ theme_id=”33690″ slug_hash=”BPexxW” default_tab=”result” user=”ablissfullemon”]See the Pen JavaScript Calculator v2.0 by Aimie | Blissful Lemon πŸ‹πŸŒΊ (@ablissfullemon) on CodePen.[/codepen_embed]

I added a bit more functionality than what the requirements specified. When I created the UI, I added a few extra buttons – ‘delete’ and %, so naturally I had to make them actually do something in return.

In case you’re curious, the ‘delete’ button deletes the last character while the % button converts whatever number is displayed into the appropriate decimal. So, 50% becomes .5, 1% becomes 0.1, and 150% becomes 1.5. This isn’t anything fancy, but it is handy for doing calculations with percentages without having to mentally convert the number into a decimal.

A Week of Celebrations

To celebrate the end of my first 100 days of code, I did absolutely nothing Sunday except grocery shopping and normal, boring adulting things.

Then Monday morning, I started working on other things that I’d been putting off for some time.

Not only did I start on a massive mound of laundry that has been slowly collecting over the last few months (towels, sheets, etc.), but I also started scrubbing the kitchen and getting organized.

Also, I was running into theme issues (yet again) on my website, so I switched once more. This time, I found a theme that I love and it seems to completely function. There were parts of my other theme that never worked from the beginning, but I didn’t have a whole lot of time to find another theme or fix the issues until now.

So, that’s what I’ve been doing the past few days.

Oh, and did I mention I’ve also been fighting a super fun ear infection? The truth is, I would have done A LOT MORE this week, but I’ve been mostly trying to take it easy these last few days.

Approaching Round Two

After I finished the first round of 100 Days of Code, I wasn’t sure what I wanted to do next. I knew I wanted to do another round, but I wasn’t sure if I wanted to wait one or two weeks before started. I decided to take a few days and think about it before committing to anything.

Then, a few days ago, I realized I still had no idea how long I was going to wait. So, I asked Twitter what they thought.

https://platform.twitter.com/widgets.js

In true Twitter fashion, they did not disappoint. I imagined the results would be a lot closer, but over 2/3 of the responses were either “Start next week” or comments that essentially said do what you feel like doing. My answer could not have been any clearer based on those results.

So, starting next week, I will be embarking on my second 100 Days of Code journey.

A Few Changes

This time I am going to do things a little bit differently. My primary goal for the first 100 days was to get comfortable enough to begin applying for web developer positions. I don’t know that I’ll ever be “ready” but that’s too bad because I’m going to start applying anyway.

That means that HOPEFULLY I’ll be starting a new job in the next month or two. Because of this, I am preparing myself for having much less time to code every day, starting from day 1.

To start, I’m only going to code 3-4 hours during the week and continue with the 1-2 hours on each day of the weekend that I started halfway through the first round. It’s likely that I will need to cut this back even more once I start working away from home, especially since I still plan to keep up with my blog and other projects as much as possible.

Side note: Andrew is going back to school in the winter, so that means we’ll be spending a lot of time together in the office once again.

Updates On My Blog

My other big change is that I’ll no longer be posting a daily update on my coding progress. Once I finish this last front end libraries project, I won’t be working on any big projects for a while. I’m going to start doing a lot of smaller challenges from Codepen, CodeSignal, and similar websites, so my updates wouldn’t be nearly as interesting.

Plus, if I’m being honest, nearly 100 days of constant blogging about the same thing that IΒ literally just worked on for 8-10 hours was really becoming a bit too much for me. I was relieved when I wasn’t blogging as much towards the end. When I posted an update, it meant so much more and wasn’t being forced out of me. Don’t get me wrong – I stillΒ love blogging, but I want to spend more time on coding and doing other things, or at least blogging about other things.

So, having said all that, I am going to be limiting my coding updates to only once or twice a week. I’ll probably blog a little bit each day but I’m not going to post it until I’m ready. If I have something significant to talk about, I’m going to save it for its own thought out, researched, and curated post much like some of my older content. I’d love to start sharing tips on web development including getting started, a much closer look at some of the things I’ve learned, and things like that. Posting fewer updates is going to allow me to have that much more flexibility to do so.

Is there anything in particular that you would like to know more about? Let me know in the comments below!

Let's chat!

%d bloggers like this: