no-bullshit
Review plans, product flows, APIs, code, and explanations for needless complexity, confusing language, wasted effort, and unsupported claims. Use when making design tradeoffs, simplifying work, reviewing usability, or explicitly asked for /no-bullshit. API naming is one application, not the whole skill.
Pinned to revision 618cfd2bc10c, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.