[Klathmon]

>you wouldn't be doing major database (or other production) changes at 3 pm in the afternoon.

Coinbase isn't dedicated to one timezone. They fully support tons of countries and have customers all over the place.

Things like this have to happen at some point, and there are benefits to doing stuff like this during "work" hours (like having all of your staff online and available)

[dmitriid]

> Coinbase isn't dedicated to one timezone. They fully support tons of countries and have customers all over the place.

What timezone are their developers in? That’s the important question in this situation.

Devs deploying changes that affect customers at the end of the devs’ workday are reckless.

[kerkeslager]

> Things like this have to happen at some point, and there are benefits to doing stuff like this during "work" hours (like having all of your staff online and available)

That sounds like a benefit to Coinbase and not to any of their customers.

[saalweachter]

Eh, if Coinbase were the stock market and only open for trading for < 8 hours a day, I'd ding them, but it's always 3pm somewhere. 3pm PDT is 6pm EDT is 10pm UTC.

[bdamm]

One can only hope that they know when their peak trading patterns generally are.

[rtpg]

The inverse (not being able to do this during work hours) means that if you find an issue you won't be able to roll out a fix in an expedited manner.

Being able to fix things while they are running is a big advantage, and tends to make the entire stack lean more towards something resilient to partial failure

[wbl]

If it shortens MTTR it's worth it. It has to be 3 PM for someone.

[qes]

Their users are far from evenly distributed across timezones.