Prefer deletion over addition
Every feature creates a maintenance obligation. Remove unnecessary steps before introducing another layer.
DESIGN RULES / 04
A small set of constraints that guide what gets built, what gets simplified and what should be removed.
Every feature creates a maintenance obligation. Remove unnecessary steps before introducing another layer.
A tool should remain understandable and dependable without someone watching every operation.
Automation should remove recurring work, not relocate it into a new dashboard or babysitting routine.
The best interface makes the right action obvious and keeps the number of decisions low.
Expose the information people need; keep incidental machinery out of the way.
Trust is earned through verifiable behavior, predictable failure handling and honest output.
Every abstraction, dependency and special case has a future cost. Spend that complexity deliberately.
THE STANDARD
“If it needs constant attention, it is already broken.”Automation should remove work, not hide it.