Shipping code that works is table stakes. The question is: does it work safely, efficiently, and maintainably? We see a lot of code that passes all tests but has: - O(n²) loops that will destroy performance at scale - Race conditions that only surface under load - Error handling that swallows exceptions silently - Hardcoded values that become tech debt within weeks These aren't bugs in the traditional sense — they're architectural time bombs. They work today and blow up next quarter. What's the worst "it works" code you've seen in production?