It's Okay to Say No
summary
Argues for refusing work that has no measurable value: a reported context-sensitive help entry that documents a no-op setting, a rushed request to turn a README into a man page by release that can wait, and an engineer’s clever but undocumented ten-variable command-line that duplicates a clear five‑step GUI. Focus is on concrete choices made, why documentation would be wrong or premature, and examples of when saying no preserves quality and sanity.
AI-written summary · about
