February: Algorithms and Web APIs

February is over, and I was both able to complete more than I had anticipated, and still be behind where I intended at the start of the year.

Most of this is due to the addition of some “new” books tailored more towards the current programming tasks I’m doing at my current job. I’ve placed these on the highest priority since the main goal this year is getting a programming job full-time.

Photo Mar 06, 10 38 35 AM.jpg
Missing one other book, Beginning ASP 3.0 by Wrox Publishing

Also, Sedgewick’s algorithm course is split into two parts, of which I completed the first this month. The last couple of sections were just lecture, no implementation, so I didn’t get much coding done for my personal study repos these past couple of weeks. The second part still hasn’t been given a release date yet, so I’ll jump into that when it comes back up. Still, I’ve been able to do a lot of coding at work.

Work Projects

Since I haven’t really mentioned them before, here are the two current projects I’m coding at work:

  1. Creating a web-based ticketing system to replace my IT departments current implementation of Spiceworks. I’ll be doing mostly back-end work on this application.
  2. Creating a web-based Network Monitoring application that constantly tests connection to our locations nationwide, so that we are alerted of any network outages. I’ve been doing both front and back-end on this application.

Most of the work I’ve done so far is getting routes and data setup with Microsoft’s ASP.NET WebAPI, and completing a simple front-end for the Network Monitor. Eventually we’ll also implement a Google Maps API to have something flashy for display.

Goals for March

Here are my current goals for March:

  1. Complete the Network Monitor in full.
  2. Start back-end work for ticketing system. Complete as much as possible.
  3. Finish the following books:
    1. SQL Queries for Mere Mortals
    2. Teach Yourself ASP 3.0 in 21 Days
    3. Review my JS/jQuery book
    4. The Art of Unit Testing
    5. Why Programs Fail: A Guide to Systemic Debugging


You can check out the progress of my 2017 studying on GitHub, or read my post about it: 2017: A Year of Learning.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s