The conventional, logical advice in software engineering is to deploy when traffic is at its lowest. For decades, this has meant the dreaded Friday night or weekend release.
That makes perfect sense for the servers. It makes absolutely zero sense for the humans running them.
Why the logical choice is the wrong choice
When you deploy on a Friday night, you are trading peak system traffic for rock-bottom human cognitive capability. You are relying on a stretched, fatigued team to spot subtle bugs and fight fires before Monday morning.
Issues that pop up bleed into the weekend, tanking morale and leading to fatigue-driven mistakes. A rested team is an efficient team, and Friday night is the enemy of rest.
The Tuesday mental model
Over my time in the tech world, witnessing countless chaotic weekend firefighting sessions, I’ve arrived at a simple mantra: Release on a Tuesday. Here is why the mid-week deployment actually works:
- Prep, not pressure: Monday is for settling in. It gives the team a day to come in fresh from the weekend, focus on the impending release, and ensure everything is primed without panic.
- The Three-Day Cushion: Releasing on a Tuesday gives you 72 hours (Tuesday, Wednesday, and Thursday) of normal business operations to monitor, address unforeseen issues, and stabilize. Without the weekend looming, teams work calmly, drastically reducing rushed decision-making.
- Peak Hour Monitoring: Yes, you are deploying during peak traffic. But observing the software’s behavior during typical weekday hours provides immediate, invaluable insights to identify bottlenecks while everyone is fully caffeinated and at their desks.
The practical upshot
For teams accustomed to weekend releases, the idea of a weekday deployment is daunting. It usually stems from entirely valid concerns about traffic and availability.
But it’s worth challenging this norm. If the idea of a Tuesday mid-morning deployment terrifies you, your problem isn’t your traffic. Your problem is that your deployment process is fragile.
The day you choose to deploy speaks volumes about your team’s preparedness. Don’t mask a fragile pipeline by sacrificing your team’s weekends. Fix the process, and give Tuesday a thought.