Is "Perfect Code" actually a myth in a fast-paced startup?

Discussion on balancing code quality with the need to ship features.

The Scenario
We’ve all been there. You have a beautiful architecture in mind—modular, DRY, and fully tested. But the deadline is in 3 hours, and the stakeholder just added a "minor" change that breaks your clean abstraction.

Do you:

1. Ship the "messy" if-else chain to meet the deadline?
2. Push back the launch to ensure the codebase stays pristine?

My Take
I’m starting to believe that "Good Enough" is a senior developer skill.
Technical debt is like a credit card it’s a tool if used wisely, but it’ll ruin you if you don't have a plan to pay it back.

Let's Discuss
Where do you draw the line?
What is the one thing you never compromise on, even under pressure? (For me, it’s database migrations!)

Drop your "shipping horror stories" in the comments! 👇