Staff Engineer (Frontend) at OakNorth Bank - Mentor - Blogger - ex-Taboola, ex-zalando
Great infographic to describe SOLID. it has been a great refresher for my own knowledge. Thanks for sharing. Personally, the S is the one i used the most, what about you? Do you actively use it within your job? #techleadership #softwaredevelopment
Technical Lead .NET | Software Engineer | SQL Server Developer | Looking for new opportunities
๐ฅ ๐๐๐๐๐ โก ๐ - ๐๐ข๐ง๐ ๐ฅ๐ ๐๐๐ฌ๐ฉ๐จ๐ง๐ฌ๐ข๐๐ข๐ฅ๐ข๐ญ๐ฒ ๐๐ซ๐ข๐ง๐๐ข๐ฉ๐ฅ๐ (๐๐๐): Each class should have a single responsibility, and that responsibility should be entirely encapsulated by the class. This makes code more modular and easier to understand. โก ๐ - ๐๐ฉ๐๐ง/๐๐ฅ๐จ๐ฌ๐๐ ๐๐ซ๐ข๐ง๐๐ข๐ฉ๐ฅ๐ (๐๐๐): Software entities (classes, modules, functions) should be open for extension but closed for modification. This encourages the use of interfaces and abstract classes, facilitating future enhancements without altering existing code. โก ๐ - ๐๐ข๐ฌ๐ค๐จ๐ฏ ๐๐ฎ๐๐ฌ๐ญ๐ข๐ญ๐ฎ๐ญ๐ข๐จ๐ง ๐๐ซ๐ข๐ง๐๐ข๐ฉ๐ฅ๐ (๐๐๐): Subtypes must be substitutable for their base types without altering the correctness of the program. This ensures that derived classes can be used interchangeably with their base classes. โก ๐ - ๐๐ง๐ญ๐๐ซ๐๐๐๐ ๐๐๐ ๐ซ๐๐ ๐๐ญ๐ข๐จ๐ง ๐๐ซ๐ข๐ง๐๐ข๐ฉ๐ฅ๐ (๐๐๐): Clients should not be forced to depend on interfaces they do not use. It's about creating specific interfaces tailored to the needs of the clients to avoid unnecessary dependencies. โก ๐ - ๐๐๐ฉ๐๐ง๐๐๐ง๐๐ฒ ๐๐ง๐ฏ๐๐ซ๐ฌ๐ข๐จ๐ง ๐๐ซ๐ข๐ง๐๐ข๐ฉ๐ฅ๐ (๐๐๐): High-level modules should not depend on low-level modules; both should depend on abstractions. Abstractions should not depend on details; details should depend on abstractions. This promotes flexibility and ease of maintenance. โป๏ธ Repost if you find it intriguing. ๐ฅ Follow Behzad Dara for more .NET tips. #dotnet #aspnetcore #csharp #solid
