Coding

Guidance for implementation, naming, refactoring, error handling, and code structure.

Entries (5)

Control hidden side effects and temporal couplingMake state changes and required operation order visible so callers can reason about behavior.

Keep functions and modules cohesiveGroup behavior that belongs together and give each boundary a focused responsibility.

Make invariants explicit at boundariesState and enforce the conditions that must remain true when data enters, changes, or leaves a system.

Name for intent and domain meaningChoose names that expose the purpose, boundary, and domain meaning of code.

Refactor in behavior-preserving stepsImprove internal structure through small changes that keep observable behavior stable and reviewable.