Day 82: SOLID Design Principle and Reading!

Read through a bunch of articles on the history of JavaScript programming and design patterns. It is taking a bit of effort for me to get comfortable with all the different designs but this is exactly where I want to be. I can code but the designs of my code are mediocre. I cannot differentiate between good and bad code outside of simple issues. To become a better developer and to build larger projects I need to tackle this area of knowledge. The challenge is taking the small scale examples and points and applying them correctly to larger scale projects. I might need to look into design docs and how they are written for software projects. Step by step! I am extremely happy for the exposure I am getting though. This is the type of stuff that helps out code reviews significantly.

TLDR;

Okay, so here are the highlights of what I did:

  • JavaScript -> Read a bunch of articles on JavaScript Design patterns and the SOLID Design Principle. This is exactly what I need to take the next step and level up my programming skills. Being able to recognize design patterns being implemented and improving the quality of my code will help me in the long run with my own projects in the future. It is difficult to recognize that your code is not scalable if you do not know what scalable code is comprised of.

Readings:

Design Patterns:

SOLID Design Principle:


Goal For Round 7 of the #100DaysofCode Challenge

This is my seventh round of the “#100daysofcode” challenge. I will be continuing my work from round five and round six into round seven. I am currently working through the book “Cracking the Coding Interview” by Gayle Laakmann McDowell. My goal is to become more familiar with algorithms and data structures. This goal was derived from my goal to better understand operating systems and key programs that I use in the terminal regularly e.g. Git. This goal was in turn derived from my desire to better understand the fundamental tools used for coding outside of popular GUIs. This in turn was derived from my desire to be a better back-end developer.

I have no idea if my path is correct but I am walking down this road anyways. Worst case scenario I learn a whole bunch of stuff that will help me out on my own personal projects.