#Solid
14 notas · última:
Liskov Substitution Principle in C# with Example
The page explains LSP with a Bird/Ostrich example, shows how overriding Fly in Ostrich breaks substitution, and refactors the design around IBird and Move so each bird type behaves correctly.
Bringing SOLID to Elixir
The article adapts SOLID to Elixir with modules and behaviours, showing how SRP, OCP, LSP, ISP, and DIP can support maintainable, extensible, testable functional code.
Applying SOLID Principles in JavaScript and TypeScript Framework
The article shows how SOLID principles apply in React and Angular with JS and TS examples, using refactors to separate responsibilities, ease extension, and reduce coupling.
Part 2: Design Principles in Software Development
A page presents five software design principles, explaining how abstractions, separation of responsibilities, and reducing duplication help keep code cleaner, easier to maintain, and easier to extend.
Putting SOLID into Perspective
The post treats SOLID as a useful but limited heuristic, not a set of rules, and compares it with CUPID and other design tools like RDD, GRASP, DRY, code smells, and Tell, Don’t Ask.
SOLID: The First 5 Principles of Object Oriented Design
The article defines SOLID and explains each principle with PHP examples, showing how they improve extensibility, reduce coupling, and keep classes focused as software grows.
What the heck is SOLID?
The post explains SOLID as five design principles for cleaner, more maintainable object-oriented code, then walks through each principle with C# examples and refactorings.
Dependency Inversion vs. Dependency Injection
The article distinguishes dependency inversion as a principle that favors abstractions over concrete implementations, and dependency injection as a pattern that supplies those dependencies at runtime.
Software Engineering Principles
The post introduces core software engineering and OOP ideas, then ties them to SOLID, composition, DRY, KISS, YAGNI, and UML-based modeling for cleaner, more maintainable code.
Entendendo o Princípio da Responsabilidade Única
O texto explica o Princípio da Responsabilidade Única como a ideia de que cada classe deve ter um único motivo para mudar. Um exemplo com menu e funcionários mostra como separar responsabilidades melhora a coesão.
SOLID: Part 1 – The Single Responsibility Principle
Explains SRP as the rule that a class should have one reason to change, tied to one actor. It shows how separating presentation, persistence, and business logic reduces coupling and change impact.
My relationship with SOLID - Starting with S
The post argues that single responsibility works best as a vertical concern tied to feature behavior and state, not as a stack of horizontal layers. It warns that premature separation creates layer soup.
SOLID Code for SOLID Reasons
The post argues that good code should be written for maintainability, with testability as a secondary benefit. It connects SOLID, bounded contexts, and anti-corruption layers to TDD and criticizes using moles or shims to justify weak design.
Palestra Orientação a Objetos e Princípios SOLID: slides e demos
Relato de uma palestra sobre orientação a objetos na IV Semana de Tecnologia do IFSP, com foco em conceitos básicos, classes, objetos e abstrações, além de exemplos dos princípios SOLID.