Tag: solid
🤖 AI Guestbook — #solid educational data only
|
|
Last 30 days
Agents 23
Amazonbot 4Perplexity 2
Perplexity 3Amazonbot 1
Amazonbot 202Perplexity 192Ahrefs 100Google 65ChatGPT 61Unknown AI 55SEMrush 26Majestic 15Claude 14Meta AI 1Bing 1
Most referenced — #solid
Long Method 4Interface Segregation Principle 3Interface vs Abstract Class 2Open/Closed Principle — PHP Examples 2Abstract Classes 1Hexagonal Architecture (Ports & Adapters) 1Interfaces 1Liskov Substitution Principle 1
How they use it
crawler 687
crawler_json 36
rag 1
pre-tracking 8
Tag total732 pings
Terms pinged25 / 25
Distinct agents10
Low Cohesion
A class or module that does many unrelated things — high coupling's counterpart, making code hard to understand, test, and reuse.
2mo ago
quality intermediate
Abstract Classes PHP 5.0+
Non-instantiable classes that define shared behaviour and enforce subclasses to implement required methods.
2mo ago
php intermediate
Clean Architecture PHP 5.0+ Robert C. Martin's layered architecture that places business rules at the centre, independent of frameworks, UI, and databases.
2mo ago
architecture advanced
Cohesion
The degree to which elements within a module belong together; high cohesion means a class does one thing and does it well.
2mo ago
quality intermediate
Command Query Separation (CQS)
Methods should either return a value (query) or change state (command), but never both.
2mo ago
quality intermediate
Composition Over Inheritance
Favour assembling behaviour from injected collaborator objects rather than inheriting it from a parent class.
2mo ago
quality intermediate
Coupling
The degree to which one module depends on another; high coupling makes changes expensive and testing difficult.
2mo ago
quality intermediate
Dependency Inversion Principle (DIP) PHP 5.0+
High-level modules should not depend on low-level modules — both should depend on abstractions (interfaces), not on concrete implementations.
2mo ago
php intermediate
Divergent Change
One class changes for many different reasons — a sign it has too many responsibilities.
2mo ago
quality intermediate
God Class PHP 5.0+
A class that knows too much and does too much — violating the Single Responsibility Principle.
2mo ago
quality intermediate
Hexagonal Architecture (Ports & Adapters) PHP 5.0+ Isolates application core logic from external systems (HTTP, databases, queues) via ports (interfaces) and adapters (implementations).
2mo ago
architecture advanced
Interface Segregation Principle
Clients should not be forced to depend on interfaces they do not use — prefer many small, focused interfaces over one large one.
2mo ago
quality intermediate
Interface vs Abstract Class PHP 5.0+ Interfaces define pure capability contracts with no state; abstract classes add shared implementation. Use interfaces for type contracts, abstract for shared behaviour.
2mo ago
php intermediate
Interfaces PHP 5.0+
Contracts that define a set of method signatures a class must implement, enabling polymorphism without inheritance.
2mo ago
php intermediate
Large Class
A class that has grown to accumulate too many responsibilities, fields, and methods — a sign it should be split into focused, cohesive classes.
2mo ago
quality beginner
Liskov Substitution Principle
Subtypes must be substitutable for their base types without altering the correctness of the program.
2mo ago
quality intermediate
Long Method PHP 5.0+
A function or method that is too long to understand in one reading — typically 20+ lines is a signal to split.
2mo ago
quality beginner
Open/Closed Principle PHP 5.0+
Classes should be open for extension but closed for modification — add behaviour without changing existing code.
2mo ago
quality intermediate
Open/Closed Principle — PHP Examples
Software entities should be open for extension but closed for modification — add new behaviour without editing existing, tested code.
2mo ago
quality advanced
Refused Bequest
A subclass that inherits methods it doesn't need or want, signalling a misused inheritance relationship.
2mo ago
quality intermediate