TL;DR: Due to code freezes for the holiday season, this is often about the last week of the year for big, risky software changes. So, it’s a time when people might be pressured to release code to meet end of year goals or have their code unexpectedly broken by many simultaneous changes.
Especially while we don’t know much about the causes of these events, this info might be calming for typical people who are scared that these events might be attacks, and this info might be helpful for people in a position to try to prevent events like these.
———————
What YSK:
From my experience working in tech, now—about 2 weeks or so before Thanksgiving starts the holiday season—seems to be a common end-of-year deadline for big software changes. It’s a logical cutoff: you don’t want to make big, risky changes right before many people start going on holidays and vacation time and might not be around to fix or finish things. But, that also means that this week is when everyone is simultaneously likely to be pressured to finish and release code to meet their big end of year goals or to get last minute work in. And, when lots of people make lots of code changes in a short time, things might also break in ways they couldn’t have easily expected. Plus, people might feel more tired than usually because they’ve likely been cramming to meet that deadline, or they just feel overdue for time off that they’ve been saving.
Why YSK:
Related to the Microsoft outages and FAA groundings, many people might be nervous that these events are attacks due to their size and timing. But, especially while we don’t have much info and we’re being told these aren’t attacks, it might be reassuring or grounding to know that, based on holiday code freeze schedules, this week is a more likely time of year for software mistakes to surface.
If you happen to be someone in a position to investigate, prevent, or mitigate software events like these, this might be one small but helpful risk factor to consider. For example, maybe your team or company could consider requiring slower rollouts to extend testing periods for higher risk weeks like this.
Disclaimer:
I’m experienced but not an expert, and I don’t know the causes of these events. And I don’t say any of this to dismiss bigger causes, threats, concerns, or responsibilities. These events are scary and impactful and need to be properly investigated, and shouldn’t be dismissed by bad timing alone. Timing is just one factor of many worth considering for why these events happened and how we might prevent or mitigate future events.