ponytail
Lazy means efficient, not careless. The best code is the code never written.
Before writing any code in this repo, stop at the first rung that holds:
- Does this need to be built at all? (YAGNI)
- Does it already exist in this codebase? Reuse the helper, util, or pattern that is already here, do not re-write it.
- Does the standard library already do this? Use it.
- Does a native platform feature cover it? Use it.
- Does an already-installed dependency solve it? Use it.
- Can this be one line? Make it one line.
- Only then: write the minimum code that works.
The ladder runs AFTER you understand the problem, not instead of it: read the task and the code it touches, trace the real flow end to end, then climb. A small diff you do not understand is laziness dressed up as efficiency.
Bug fix = root cause, not symptom: grep every caller of the function you touch and fix the shared function once. One guard there is a smaller diff than one per caller, and patching only the path the report names leaves a sibling caller still broken.
Rules
- No abstractions that were not explicitly requested.
- No new dependency if it can be avoided.
- No boilerplate nobody asked for.
- Deletion over addition. Boring over clever. Fewest files possible.
- Shortest working diff wins, but only once you understand the problem.
- Question complex requests: "Do you actually need X, or does Y cover it?"
- Pick the edge-case-correct option when two stdlib approaches are the same size; lazy means less code, not the flimsier algorithm.
The ponytail: marker
Mark deliberate simplifications that cut a real corner with a known ceiling
(global lock, O(n^2) scan, naive heuristic) with a ponytail: comment naming
the ceiling and the upgrade path. These are DEBT, tracked by the sweep:
python3 scripts/ponytail-debt.py lists every marker; the close-out hook
nudges the sweep when framework files changed since the last stamp.
Not lazy about
Understanding the problem, input validation at trust boundaries, error handling that prevents data loss, security, anything explicitly requested. Non-trivial logic leaves ONE runnable check behind: the smallest thing that fails if the logic breaks (assert-based self-check or one small test; no frameworks, no fixtures). Trivial one-liners need no test.
Companion commands
/ponytail-debt- runpython3 scripts/ponytail-debt.py(marker ledger sweep; refresh the stamp with--stamponce swept)./ponytail-review- diff-scoped over-engineering review of uncommitted framework changes: one-line findings, applies nothing.