Tagged articles
DRY
30 articles · Page 1 of 1
This article breaks down Palantir's four prioritized ontology modeling principles—domain-driven design, DRY with Rule of Three, open/closed extension, and composition over inheritance—illustrating each with concrete anti-patterns and a practical 12-question review checklist to prevent model fragmentation as teams scale.
Composition Over InheritanceDRYModeling Review Checklist
0 likes · 20 min read

The article argues that merely knowing popular coding principles is insufficient, and it provides concrete decision frameworks, code examples, and trade‑off analyses for DRY, KISS, YAGNI, POLA, the Boy Scout Rule, Fail‑Fast, and Separation of Concerns so developers can choose when to abstract, simplify, defer implementation, ensure expected behavior, improve incrementally, expose errors early, and isolate change boundaries.
DRYKISSPOLA
0 likes · 14 min read

The article explains that developers often memorize dozens of rules such as DRY, KISS, YAGNI, SOLID, and CAP, yet still produce poor code because they misunderstand the original intent of these principles, illustrating the pitfalls with concrete examples, classic laws like Brooks' Law, and how mis‑interpretations cascade through design, architecture, and measurement practices.
CAP theoremDRYKISS
0 likes · 17 min read

The article explains the YAGNI principle, showing how focusing on current requirements, using simple solutions, and refactoring when real needs arise can prevent over‑engineering, reduce technical debt, and keep Java code clean and adaptable.
DRYJavaKISS
0 likes · 7 min read

The article clarifies that the DRY principle targets hidden knowledge duplication rather than superficial code similarity, explains why over‑abstraction can be harmful, and provides concrete Java examples of both violations and correct applications, while also discussing how to balance DRY with YAGNI.
DRYJavaYAGNI
0 likes · 10 min read

This article explains the core software design principles KISS, DRY, and SOLID, shows why they matter for readability and maintainability, provides concrete Java examples and step‑by‑step guidelines, and lists actionable rules developers can follow to write cleaner, more reusable code.
Clean CodeDRYKISS
0 likes · 19 min read


21CTOOct 11, 2024 · Fundamentals
This article shares a developer’s journey from tangled, hard‑to‑read code to clean, maintainable software, illustrating how meaningful naming, PEP 8 compliance, static typing, small functions, avoiding magic numbers, and the DRY principle can dramatically improve code quality.
Best PracticesClean CodeDRY
0 likes · 9 min read

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.
DRYYAGNIabstraction
0 likes · 3 min read

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.
ComplexityDRYDesign Principles
0 likes · 18 min read


DevOpsJan 2, 2024 · Fundamentals
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.
DRYDesign PrinciplesSOLID
0 likes · 18 min read

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.
DRYLaravelModules
0 likes · 6 min read

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.
ComplexityDRYDesign Principles
0 likes · 19 min read

The article explains why maintainable, human‑readable code matters for evolving software, outlines core concepts like high cohesion and low coupling, details the SOLID and other practical principles, and describes common refactoring techniques to improve readability and flexibility.
DRYKISSSOLID
0 likes · 6 min read


21CTOJul 12, 2023 · Fundamentals
This article explores essential software engineering practices—including the DRY principle, SOLID design principles, common design patterns, high‑availability architecture, automation, effective communication, and career development—offering concrete examples, code snippets, and actionable advice to help developers write cleaner, more maintainable, and scalable code.
Best PracticesDRYHigh Availability
0 likes · 31 min read

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.
BackendDRYHigh Availability
0 likes · 30 min read

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.
DRYPHPbackend development
0 likes · 7 min read

The article examines whether over‑designing code adds value by exploring core software design principles such as KISS, YAGNI, DRY, and Simple Design, illustrating each with concrete examples, refactoring snippets, and practical guidelines to help developers balance simplicity and functionality.
DRYKISSYAGNI
0 likes · 9 min read

This article compiles essential programming principles such as KISS, DRY, YAGNI, and others, explaining their origins, practical advice, and additional design guidelines to help developers write simpler, more maintainable, and less error‑prone code.
Code MaintainabilityDRYKISS
0 likes · 10 min read

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.
Best PracticesDRYKISS
0 likes · 12 min read

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.
Code MaintainabilityDRYKISS
0 likes · 11 min read

Learn how to write readable, maintainable, and reusable methods by applying core design principles such as Single Responsibility, KISS, and DRY, along with practical naming conventions, parameter handling, method size guidelines, and code structuring techniques illustrated with Java examples.
Clean CodeDRYDesign Principles
0 likes · 17 min read

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.
Clean CodeDRYKISS
0 likes · 12 min read

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.
Clean CodeCode MaintainabilityDRY
0 likes · 11 min read

This article compiles essential programming principles such as KISS, DRY, YAGNI, and Code for the Maintainer, explains their origins, practical applications, and concrete guidelines to help developers write simple, maintainable, and efficient code while avoiding unnecessary complexity.
Code MaintainabilityDRYKISS
0 likes · 12 min read

This article explains core software design principles—including KISS, DRY, high cohesion/low coupling, separation of concerns, YAGNI, the Boy‑Scout rule, and the SOLID rules—detailing their motivations, practical guidelines, benefits, and common pitfalls for creating maintainable, flexible code.
Clean CodeDRYKISS
0 likes · 27 min read

The article explains why copy‑pasting code (CV) creates maintenance nightmares, shows how to identify structural and conditional duplication, and provides concrete refactoring steps—extracting methods, using common interfaces, and applying functional techniques—to achieve DRY and improve code readability.
DRYcode duplicationrefactoring
0 likes · 8 min read

The article argues that code should primarily be written for human readers, emphasizing principles like KISS and DRY, thoughtful commenting, avoiding TODOs, and the necessity of unit tests, while acknowledging trade‑offs and offering practical guidance for producing maintainable, elegant software.
Clean CodeCode ReadabilityDRY
0 likes · 12 min read

This article explores why clean, readable code matters, explains key principles such as KISS and DRY, discusses the role of comments, unit tests, and avoiding TODOs, and offers practical advice for developers to improve code quality and long‑term maintainability.
Best PracticesClean CodeDRY
0 likes · 11 min read


21CTOJun 7, 2020 · Fundamentals
This article explains the DRY (Do Not Repeat Yourself) principle, demonstrates how duplicated PHP code in a Report class can be refactored by extracting shared logic into reusable methods, and shows the final clean implementation that improves readability and maintainability.
Best PracticesDRYPHP
0 likes · 7 min read

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.
DRYDesign PrinciplesKISS
0 likes · 10 min read
