The author shares personal reflections on OOP, SOLID, composition versus inheritance, design patterns, and layered architecture while recounting a recent project refactoring experience and emphasizing practical insights over textbook theory.
This article summarizes the most widely used object‑oriented design principles—including the five SOLID rules, the Composite/Aggregate Reuse Principle, the Law of Demeter, and related guidelines—explaining their definitions, analyses, advantages, and practical examples for improving software modularity and maintainability.
This article explains why unit testing is essential for PHP projects, introduces SOLID design principles, shows how to choose and install PHPSpec, demonstrates writing specifications, mocking, argument matching, exception testing, and configuring code‑coverage reports, all with concrete code examples.
This article summarizes the core object‑oriented design principles—including SOLID, the Law of Demeter, and composition/aggregation reuse—explaining their definitions, analyses, advantages, and real‑world examples to help developers write more maintainable and extensible software.
This article summarizes key object‑oriented design principles—including the SOLID rules, Dependency Inversion, Interface Segregation, Composite/Aggregate Reuse, and Law of Demeter—explaining their definitions, analyses, advantages, and practical examples such as Spring MVC component separation and Java code illustrations.
This article explores software architecture fundamentals, covering object‑oriented design principles, SOLID, DRY, KISS, logical vs. physical layers, service and business logic layers, SOA, data access strategies, stored procedures, and the MVC pattern, providing practical insights for building maintainable systems.
This article explains the six core SOLID principles, introduces additional design guidelines such as composition, acyclic dependencies, and Hollywood principle, and lists other essential software design rules like DRY, KISS, high cohesion, and separation of concerns to help developers build robust, maintainable systems.
Frank, a senior technical expert at Alibaba International, shares how his team tackled the growing complexity of their legacy CRM system by redesigning the architecture with extensible extension points, metadata, CQRS, DDD, SOLID principles, and disciplined layering to achieve better scalability, maintainability, and code readability.
This article summarizes key software design principles such as DRY, KISS, SOLID, New Jersey style, Separation of Concerns, and YAGNI, explaining their meanings, benefits, and practical code examples for writing cleaner, more maintainable code.
This article introduces Java developers to essential object‑oriented design principles—including DRY, encapsulation, Open/Closed, SRP, DIP, composition over inheritance, LSP, and Interface Segregation—explaining their benefits, proper usage, and common pitfalls to help write high‑cohesion, low‑coupling code.
