First: "a well-deserved break" has a very specific connotation in certain teams, due to an ill-timed comment from a certain meta-team a few years ago. It was read as wicked condescending at the time, and it will not cause grudges to be let go if anything like it is said again by that particular team.
Second: so AD&T wouldn't get a break, because they'd be writing the code change? Or the testers? Or Docs and Support (and possibly PAC), who'd have to be changing documents internal and external to deal with the new code?
Second, related: for giggles, some time, head to github, and look at the list of authors for pull requests. Some past authors aren't listed, and private github accounts aren't, so you can round up a little.
Third: the "omg the sky is falling! Get my fic off there and delete my account!" contingent would mean an absolute flaming mess for Comms and, frankly, Support to deal with when we turned things back on.
Third, dependent: because we pretend to be GDPR and CCPA and DMCA compliant, we cannot put the database in a hard read-only unless we take the whole site offline and queue the requests to process before it comes up. And we'd not be able to process GDPR/CCPA information requests while the db is down - damned both ways.
I...have many more thoughts, but this spoon is getting pretty sharp, so I'm going to wander off for now.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
This is my last spoon. Sorry.
Date: 2023-05-29 01:54 am (UTC)Okay, so.
I appreciate the theory. I do.
But. Some thoughts.
First: "a well-deserved break" has a very specific connotation in certain teams, due to an ill-timed comment from a certain meta-team a few years ago. It was read as wicked condescending at the time, and it will not cause grudges to be let go if anything like it is said again by that particular team.
Second: so AD&T wouldn't get a break, because they'd be writing the code change? Or the testers? Or Docs and Support (and possibly PAC), who'd have to be changing documents internal and external to deal with the new code?
Second, related: for giggles, some time, head to github, and look at the list of authors for pull requests. Some past authors aren't listed, and private github accounts aren't, so you can round up a little.
Third: the "omg the sky is falling! Get my fic off there and delete my account!" contingent would mean an absolute flaming mess for Comms and, frankly, Support to deal with when we turned things back on.
Third, dependent: because we pretend to be GDPR and CCPA and DMCA compliant, we cannot put the database in a hard read-only unless we take the whole site offline and queue the requests to process before it comes up. And we'd not be able to process GDPR/CCPA information requests while the db is down - damned both ways.
I...have many more thoughts, but this spoon is getting pretty sharp, so I'm going to wander off for now.