Understanding the SOLID principles

This week's blog, Undestanding the SOLID principles is a book section written by Edward Guiness really short, but full of important lessons and advices for correct implementation. One thing I like from lectures, articles and readings like this one is that it does not leaves the reader to find out the practical approach (as many times this are just presented theoretically). Now the author properly presents each one of the principle and tries to explain it with a code example (even though the code examples are quite obvious, it helps to learn and confirm where the principle can be applied). 

While learning how to code, throughout my entire computer science major I had the privilege to attend classes where the teacher was doing some live coding. There, we knew how the process of turning an algorithm into code was. I remembered that teacher Roberto Martínez always warned us about first designing a clear and accurate solution and not jump straight ahead to code. That is the difference between programmers and software engineers, we understand that coding is not just typing in the keyboard, but a bigger process that involves designing, debugging, applying principles (like SOLID), refractor for the code to be easier to mantain and finally software design patterns to make the best possible program.

I would like to conclude my blog post with an advice. A software engineer always needs to be open to the arrival of new technologies, perhaps they will last for months, or perhaps they will evolve the role of programming for the following years. But I am sure of one thing, applying the correct patterns and principles in our code will always be present, so it does not matter if you program in Python, Javascript, C, C++, Ruby, etc, you should always look for best practices.