I built a CLI that roasts HTTP status codes instead of just logging them

Terminal output during local dev is boring. A 500 error scrolls by as a single dim line and you barely notice it. A 429 from a rate limiter looks identical to a successful 200. Your server is quietly screaming and your log file is a wall of near-identical text. I got fed up with this over a weekend and built roastttp — a tiny CLI and Express middleware that reacts to HTTP status codes with dry, dev-sarcastic one-liners and ASCII art. npx roastttp https://httpbin.org/status/500 POST /api/payment