Five SOLID principles give guidelines on how to organize code into classes:
Single responsibility,
Open-close,
Liskov substitution,
Interface segregation,
Dependency inversion.
Robert Martin is a developer, acclaimed speaker at conferences worldwide, and the author of many books including:
The Clean Coder, Clean Code,
Agile Software Development: Principles, Patterns, and Practices, and UML for Java Programmers.
Interview gives a picture on how to think while
designing software using SOLID.
2 comments:
Is Singleton a pattern or anti-pattern according to SOLID principles?
It may be treated as anti-pattern because there are more than one responsibility of Singleton class (instantiation and real singleton's functionality)
Post a comment