Every developer knows the week. The date was agreed months ago, back when it felt comfortably far away. Now it's on the calendar with a little red dot, and the little red dot is looking at you.

Here's a field report from a typical deadline week, followed by the things that genuinely help. Any resemblance to your own week is entirely intentional.

Monday: the age of optimism

❌ "We're basically done. Just a few small things left."

The few small things are listed in a ticket called "Final bits". It has nineteen sub-tasks. Three of them say "TBD".

❌ You estimate each remaining task at "an hour, maybe two". You've been estimating like this for years. You have never once been right. Today feels different.

Tuesday: the discovery

❌ You open the "small" task and find out it touches the payments flow, the mobile app, and a report nobody has looked at since it was built.

❌ A dependency needs updating. The update needs another update. You are now reading a changelog from a library you didn't know you used.

❌ Someone asks, "Could we also quickly add...?" The word "quickly" is doing heroic work in that sentence.

Wednesday: the negotiation with physics

❌ You calculate the remaining work and the remaining hours. The numbers disagree. You decide the numbers are being pessimistic.

❌ Your status update says "on track". Technically you are on a track.

Thursday: the bargaining stage

❌ "What if we skip the tests just this once and add them next week?" Next week has never heard of these tests and never will.

❌ You've had four coffees and written six lines. Two of them are console.log.

❌ The bug that only happens in staging appears. Of course it does. It's Thursday.

Friday: the deploy

❌ It's 5:40pm. The build is green. Everyone is looking at the deploy button the way people look at a cake that might be a prank.

❌ You deploy. You refresh. You refresh again. You keep your laptop open all evening "just in case", which is a very relaxing way to start a weekend.

What actually gets you through it

The funny part is that most of deadline week is decided long before deadline week. These are the habits that genuinely change how it goes.

✅ Cut scope early, not late. Sort the remaining work into must-have, should-have and nice-to-have, and agree the list with whoever owns the deadline. Cutting a feature on Monday is a decision. Cutting it on Friday is a crisis. A smaller thing that works beats a bigger thing that's broken.

✅ Say it out loud, early. The moment you know the date is at risk, tell someone, and bring options: "We can ship on time without the export feature, or ship everything three days later." Managers can work with bad news on Tuesday. Nobody can work with a surprise on Friday afternoon.

✅ Protect your focus. Block time in your calendar, mute non-urgent channels, and batch questions. Deadline week is exactly when "quick calls" multiply. A few hours of deep focus does more than a whole day of interruptions.

✅ Keep the safety net. Skipping tests feels faster for about a day. Then you're debugging in production with less sleep. Keep the critical tests, especially around money and data, even if the nice-to-have tests wait.

✅ Make the deploy boring. Deploy earlier in the day, earlier in the week if you can, with a rollback plan you've actually tried. Feature flags let you ship code switched off and turn it on when you're ready. A Friday evening deploy should never be the plan; at worst it's the exception.

✅ Say no to "quickly", politely. "Happy to, after the release" is a complete sentence. Write it down so it's not forgotten, and so it doesn't sneak into this week.

✅ Sleep. Tired developers write bugs that take rested developers days to find. The all-nighter feels heroic and usually costs more than it saves.

And next time

After the release, take twenty minutes for a short retrospective. What did we underestimate? What did we discover too late? Which "small thing" wasn't? That's how next quarter's deadline week becomes a slightly less dramatic one.

What's your deadline-week survival trick? And be honest: what's the latest on a Friday you've ever pressed deploy?