KISS · DRY · YAGNI · naming — development philosophy
Choosing to write docs and comments in a native language other than English is a decision development teams in non-English-speaking regions often face. This article covers the convention of separating identifiers (Engli…
These three acronyms are often cited together as software design principles. Their origins and meanings differ slightly, and some interpretations even conflict. This article covers the origin, intent, and frequently con…
Feature flags (a.k.a. feature toggles) are a pattern frequently cited from large-company case studies. Small teams sometimes carry the same expectations into them, but cost and benefit vary by environment. This article…
Several books and studies discuss what "good names" are. This article organizes facts from Clean Code, Code Complete, Mythical Man-Month, and Cognitive Load theory.
Trying to fix every problem in one big refactor often fails. A pattern of steady cleanup in small units tends to produce more stable results — a common observation. This article covers the Boy Scout Rule and the Strangl…
A repository hosts documents for two kinds of readers: humans, and code-assistant agents (LLM-based IDE assistants and AI coders). This article covers the standards and conventions for both.
As LLM-based code assistants become routine, "how should we mark that AI helped?" has split into different team decisions. This article objectively organizes the relevant facts (lawsuits, OSS license positions, commit t…
The phrase "best practice" is often applied without question, but a single answer that fits every environment equally is rare. This article covers facts from three classics (CAP, PACELC, Conway's Law) that show context…
A folder structure is not just file classification — it can become a device that promises dependency direction and the scope of change between code modules. This article covers facts about Feature-Sliced Design, Domain-…
SSOT (Single Source of Truth) started as a data governance term and has expanded into a principle for code, documentation, and schema operations. This article covers the origin, areas of application, and trade-offs.