3 ms·

> but if there happened to be an outage during that time now you’d have to have your team working then anyway. So you're having them work late 52 times a year

> but if there happened to be an outage during that time now you’d have to have your team working then anyway. So you're having them work late 52 times a year AND when there's an outage vs only when there's an outage. They're working late WAY more in your plan.

endisneigh 5y ago
The existence of planned downtime doesn’t mean they have to work during said time. I’m not following your reasoning
- kabdib 5y ago
  Er, you bring the service down so you can do work on it. Somebody is doing that work. I guarantee that you'll have trouble hiring qualified people for a role that includes core hours of "2AM-5AM Sunday mornings" (or whatever other oddball time you've decided). Updating systems is precisely when you may need to have all-hands-on-deck responses. Been there, multiple times.
- sigstoat 5y ago
  they might not have to work during every planned downtime, but they're going to have to work during some of them, or what was the point of the downtime?
  - endisneigh 5y ago
    The point is to create a predictable period in which downtime, if any, would occur during
    - xmprt 5y ago
      This predictability only matters for frequent, repeat customers. But those are the exact customers that you could just email saying "the website is going to be down on Sunday for 1 hour for planned maintenance" a few times a year when it's actually required. If you run a business (eg. HFT where you run certain cleanup scripts after trading hours) where regular planned downtime is fine then go for it but most of the time, you don't need a downtime schedule every single week because you're not doing planned maintenance work every single week.
      - endisneigh 5y ago
        I think people are getting too caught up in my particular example. It could be a month, biweekly, etc.
      - ohyeshedid 5y ago
        You will be doing that every week when the system is designed to only be worked on during those planned windows, because that's what happens in these types of situations. These windows are also when people discover how fragile their infrastructure is; when it doesn't come back up and now everyone is panicking and well past the planned downtime window.

endisneigh 5y ago

The existence of planned downtime doesn’t mean they have to work during said time. I’m not following your reasoning

kabdib 5y ago
Er, you bring the service down so you can do work on it. Somebody is doing that work. I guarantee that you'll have trouble hiring qualified people for a role that includes core hours of "2AM-5AM Sunday mornings" (or whatever other oddball time you've decided). Updating systems is precisely when you may need to have all-hands-on-deck responses. Been there, multiple times.
sigstoat 5y ago
they might not have to work during every planned downtime, but they're going to have to work during some of them, or what was the point of the downtime?
- endisneigh 5y ago
  The point is to create a predictable period in which downtime, if any, would occur during
  - xmprt 5y ago
    This predictability only matters for frequent, repeat customers. But those are the exact customers that you could just email saying "the website is going to be down on Sunday for 1 hour for planned maintenance" a few times a year when it's actually required. If you run a business (eg. HFT where you run certain cleanup scripts after trading hours) where regular planned downtime is fine then go for it but most of the time, you don't need a downtime schedule every single week because you're not doing planned maintenance work every single week.
    - endisneigh 5y ago
      I think people are getting too caught up in my particular example. It could be a month, biweekly, etc.
    - ohyeshedid 5y ago
      You will be doing that every week when the system is designed to only be worked on during those planned windows, because that's what happens in these types of situations. These windows are also when people discover how fragile their infrastructure is; when it doesn't come back up and now everyone is panicking and well past the planned downtime window.