Day 85: Tightly vs. Loosely Coupled Code

The subject of code testing got interesting when I read a great article. I learned a ton from the article and it gave me a lot to think about within my own code. I have always wondered how exactly do you write scalable code. I have not written code for programs used by billions of users so how do I know if my code sucks or not. Today I learned one key aspect of scalable code is that it is loosely coupled. This means that functions, objects, etc. are not not heavily dependent on any other code to run. They can operate individually. I have been aware of this concept for a while but implementing it is not the easiest thing in the world. Testing is one method of checking code quality. Tightly coupled code is far more difficult to test when compared to loosely coupled code. This alone has me valuing testing way more and has gotten my engagement level up. I now want to write better tests on my projects to build better habits.

TLDR;

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



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.