How I Learned To Write SOLID Code

Learning the Object-Oriented design principles

Mike Wolfe
CodeX

--

Photo by Joshua Bartell on Unsplash

The best part about programming, in my opinion, is that there’s always something to learn. Whether you’re a beginner, senior developer, or somewhere in between, there’s always something you could learn. At least in terms of Object-Oriented Design (OOD), even between languages, you may find common practices that are adopted. The more experience you have, the easier it is to put each principle into practice, but it’s something you may have been using, at least in part, since day one. The principles I’m referring to are SOLID.

SOLID principles for OOD was a term I hadn’t heard before this week. However, as I read more about what the principles are, I realized that they represented some of the standard practices for “good” code that I have been learning through my years of experience. No matter what level of experience you are, they are incredibly useful to understand. However, while doing my research on what SOLID stood for, I found that a lot of the articles describing it aren’t quite as beginner-friendly. Some used difficult terms or simply just answered with examples that didn’t always make sense. Even though I could get a basic idea of what each principle was, I could see now why I hadn’t learned about SOLID as a beginner. So, this is where I decided to write an article that could…

--

--

Mike Wolfe
CodeX
Writer for

Software Developer, Tech Enthusiast, Runner. Current project http://sqlcheater.com/ Connect with me on LinkedIn: www.linkedin.com/in/michael-wolfe-176212125