You know that developer who keeps insisting their code works fine despite failing every single test? Yeah, they're about to say "quick win" for the 47th time today while proposing yet another "temporary" workaround that'll definitely become permanent technical debt. The intensity in those eyes isn't anger—it's the pure, concentrated frustration of a senior dev who's heard "quick win" used to justify skipping unit tests, hardcoding API keys, and deploying directly to production on a Friday afternoon. Say it one more time and watch them write a 3000-word RFC on proper development practices. Pro tip: If someone calls something a "quick win" more than twice in one sprint planning meeting, it's neither quick nor a win. It's usually a shortcut that'll haunt your codebase like a ghost in the machine.