How do I maintain integrity when asked to ship code I know isn't ready?
This is where your character actually gets tested. Not when doing the right thing is easy. I see engineers cave here because they're scared: of letting down their manager, of looking slow, of losing standing. But you have to tell real pressure apart from noise. If the code truly isn't ready, say so. Name the exact risk: "If we ship this, we're probably looking at a production outage in these situations." Then say what "ready" looks like and how long it takes. Sometimes the call is "ship it anyway." That's management's decision if they're willing to accept the risk. What you can't do is pretend you didn't know. That's where you lose your integrity, and once it's gone, it's harder to rebuild than any piece of code. Here's the strange part. When you're honest about what you know and don't know, people trust you more, even when they don't like the answer. You become someone whose judgment counts. That's worth more than shipping fast.