What’s the most un-ignorable code failure feedback loop you’ve ever seen?

When building

(a local-first Mac security auditor), I realized that standard static analysis tools are too easy to ignore. They spit out a wall of text in the terminal or a dashboard, and developers just clear the screen or filter it out.

To fix that, I built "Roast Mode." The second the engine catches a severe security exploit or hardcoded secret locally, it triggers heavy trackpad haptics and uses native voice synthesis to sarcastically mock your code errors out loud. It forces you to fix the bug just to make it shut up.

It got me thinking: what is the most creative, brutal, or un-ignorable feedback loop you've ever experienced or built to force better development habits? (Bonus points if it involved physical hardware or pure developer humor!)