It's been six years since we've had any significant issues with the clock shifts when Daylight Saving Time occurs. However, every time we schedule a Teams meeting with various QA users, sysadmins, and cybersecurity personnel, we still perform tests after the time change to ensure nothing is broken. This usually takes place late at night and often seems unnecessary because everything appears to be functioning normally. I worry that if we ever stop these tests, something might go wrong, and then I'd be responsible for it. Is this still a common practice for others, or are we just lagging behind?
3 Answers
It really varies by company. If you have different sales platforms in various regions communicating with a central backend, it can be wise to double-check that transactions came through without problems. I've learned to avoid scheduling batch jobs around the clock change to minimize hassle.
Honestly, most systems should be operating on UTC, so if everyone adheres to that standard, you shouldn't feel the effects of Daylight Saving Time. That's how it should ideally be set up!
As a manager, I just brace myself for the inevitable emails from team members who are late or unavailable that Monday after the clock shift. It's wild how some adults can't seem to keep track of time changes!
Right? My usual strategy is to ignore meeting reminders and hope for the best!
Mistakes happen, though! I once missed a flight because the daylight saving time change affected my schedule. It's a real headache sometimes!