User Tools

Site Tools


clean_code

Clean Code

Return to Doc Martin

Snippet from Wikipedia: SOLID

In software engineering, SOLID is a mnemonic acronym for five design principles intended to make object-oriented designs more understandable, flexible, and maintainable. The principles are a subset of many principles promoted by American software engineer and instructor Robert C. Martin, first introduced in his 2000 paper Design Principles and Design Patterns discussing software rot.: 2–3 

The SOLID ideas are

  • The Single-responsibility principle: "There should never be more than one reason for a class to change." In other words, every class should have only one responsibility.
  • The Open–closed principle: "Software entities ... should be open for extension, but closed for modification."
  • The Liskov substitution principle: "Functions that use pointers or references to base classes must be able to use objects of derived classes without knowing it." See also design by contract.
  • The Interface segregation principle: "Clients should not be forced to depend upon interfaces that they do not use."
  • The Dependency inversion principle: "Depend upon abstractions, [not] concretes."

The SOLID acronym was introduced later, around 2004, by Michael Feathers.

Although the SOLID principles apply to any object-oriented design, they can also form a core philosophy for methodologies such as agile development or adaptive software development.

Best Practices: IaC Best Practices, GitOps Best Practices, Cloud Native Best Practices, Programming Best Practices, DevOps Best Practices, Programming Style Guides, Clean Code, Pragmatic Programmer, Git Best Practices, Continuous Integration CI Best Practices, Continuous Delivery CD Best Practices, Continuous Deployment Best Practices, Code Health Best Practices, Refactoring Best Practices, Database Best Practices,

Dependency Management Best Practices (The most important task of a programmer is dependency management! - see latest Manning book MEAP, also Dependency Injection Principles, Practices, and Patterns)

Continuous Testing and TDD Best Practices, Pentesting Best Practices, Team Best Practices, Agile Best Practices, Meetings Best Practices, Communications Best Practices, Work Space Best Practices, Remote Work Best Practices, Networking Best Practices, Life Best Practices,

Agile Manifesto, Zen of Python, Clean Code, Pragmatic Programmer

(navbar_best_practices)


© 1994 - 2024 Cloud Monk Losang Jinpa or Fair Use. Disclaimers

SYI LU SENG E MU CHYWE YE. NAN. WEI LA YE. WEI LA YE. SA WA HE.


clean_code.txt · Last modified: 2024/04/28 03:42 (external edit)