SOLID Programming Principles

Single Responsibility Principle, Open Closed Principle, Liskov Substitution Principle, Interface Substitution Principle, Dependency Inversion Principle, DRY Principle

This topic was requested to me by a user on twitter. If you have any topic requests, my DMs are open.

This is mostly for those who will work with Software/Tech companies, MLEs, and those who do heavy Python usage.

Basically, Quants don’t care, and neither do those who work with R.

The principles originally came from a guy named Robert C Martin. The paper was called Design Principles, and design patterns. A picture of Robert is below:

Robert C Martin

Robert is also known for writing his book called “Clean Code”, and the “Agile Manifesto”.

Table of Contents

1. Software Development

2. Single Responsibility Principle

3. Open Closed Principle

4. Liskov Substitution Principle

5. Interface Segregation Principle

6. Dependency Inversion Principle

If you just want to see all 5 of the SOLID principles. Here's a picture:

SOLID Design Principles

1 - Software Development

Software development principles are essential concepts that guide software engineers and machine learning engineers. These design principles help ensure that developers create code that is maintainable, reliable, and secure. They provide a framework for understanding how to make decisions about the structure, design, and implementation of software projects. If you work in IT, for a software company, you'll need to know this. In other words, the professions are:

• Software Engineer

• Machine Learning Engineer

• Data Engineer

• Dev Ops

The 5 principles put together make you the word SOLID. SOLID helps you outline the best practices around writing understandable code with fewer errors while making it easier to modify existing implementations while minimizing duplication of effort or code complexity. This can free up valuable time spent debugging or refactoring long ago written error-prone code by establishing standard designs which allow future changes easily when applicable needs arise.