1 views collected around this technical thread.
The article argues that in early development stages, a small amount of code duplication should be tolerated, warning against premature DRY abstractions that can lead to over‑engineered designs, and advises waiting for genuine common patterns before introducing shared abstractions.
This article explains essential software architecture concepts such as entropy and broken‑window effects, the sources and symptoms of complexity, the importance of orthogonality and consistency, and classic design principles like SOLID, DRY, and layered abstraction to guide architects in building maintainable, flexible systems.
This article explores the fundamentals of software architecture, discussing entropy, the dual value of behavior and structure, core design principles such as SOLID, DRY, layering, orthogonality, component coupling, boundary definition, communication patterns, and modeling tools, while also offering practical guidance for building maintainable systems.
ZapCraft is a Laravel package that automates the creation of entity‑related files, enforces SOLID and DRY principles, and integrates with Laravel‑Modules to streamline backend development while providing ready‑made repositories, services, requests, resources, and API routes.
The article explains that good software architecture must be deliberately designed and continuously refactored to combat entropy and the broken‑window effect, balancing behavior and architecture value while managing complexity through principles like Ockham’s razor, orthogonality, DRY, stable dependencies, layered abstractions, and clear boundaries, supported by UML visualizations.
A senior Tencent Cloud backend engineer outlines practical best‑practice guidelines—applying DRY and SOLID principles, leveraging common design patterns, designing high‑availability architectures, automating workflows, prioritizing value‑driven development, fostering clear communication, ensuring reliability, and encouraging continuous learning—to write clean, maintainable, and resilient backend systems.
This article explains how to remove duplicate and redundant PHP code by applying refactoring principles such as the DRY rule, using functions and classes, adopting naming conventions, simplifying conditionals, and externalizing configuration, thereby improving readability, maintainability, and performance.
This article compiles essential software development principles such as KISS, DRY, YAGNI, Code for the Maintainer, and related guidelines, explaining their origins, practical applications, and why adhering to them leads to simpler, more maintainable, and higher‑quality code.
This article explains essential software design principles such as KISS, DRY, YAGNI, and additional guidelines for writing maintainable, simple code, while also warning against over‑engineering and emphasizing the importance of testing, clear communication, and minimal coupling in everyday programming practice.
This article presents a concise collection of essential programming principles—including KISS, DRY, YAGNI, writing code for maintainers, lazy development, and testing discipline—explaining their origins, practical applications, and how they help developers produce simpler, more maintainable, and higher‑quality software.
This article outlines essential programming principles—including KISS, DRY, YAGNI, and Code for the Maintainer—explaining their origins, practical applications, and how they help developers write simpler, more maintainable, and less error‑prone software.
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.