There were outages around the same time last year. Somebody in the HN thread commented back then that the employees evaluation and promotion window ends around december/eoy, thus more releases are made. https://en.m.wikipedia.org/wiki/Google_services_outages
Some people are definitely not gatting a raise.
More likely someone actually will. A blameless postmortem will be written, and the people that will fix the bug or systems issue will have something to work on with high visibility and high impact, which tends to translate in good performance ratings.
Well, there are various whitepapers that reformulate this exact truth you've highlighted: issues tend to happen more when changes are made. Regarding the technical details doc, Google will never state that outright in individual postmortems. And they will definitely not draw this to the logical conclusion regarding the spiky yearly activity.
> logical conclusion regarding the spiky yearly activity Why is it logical? There’s tons of changes being deployed at all times, at all large companies. Across products, verticals, everything - hundreds of changes at any given point. Some of these changes can introduce hard-to-predict bugs in globally distributed systems. Most of the time, external users don’t even notice before they’re fixed. Like another commenter…
> Like another commenter said, performance reviews do not coincide with with the year-end at Google and other companies.
When are they? My bet is that they're roughly around the same time period, even if they don't start or close on December 31st.
There were outages around the same time last year. Somebody in the HN thread commented back then that the employees evaluation and promotion window ends around december/eoy, thus more releases are made. https://en.m.wikipedia.org/wiki/Google_services_outages
November 11 is a public holiday in US. And it seems it has in recent years became a company holiday in many companies too. May be that break in established over many years cadence of workday and holidays plays a role here, like say affecting smoothness of support transition between US-EMEA-APJ.
Nothing wrong with it. People make errors, distributed systems aren't easy. More frequent changes - more likely a bug was introduced. My post is just a speculation, let's wait for the actual technical details doc from Google.
Well, there are various whitepapers that reformulate this exact truth you've highlighted: issues tend to happen more when changes are made. Regarding the technical details doc, Google will never state that outright in individual postmortems. And they will definitely not draw this to the logical conclusion regarding the spiky yearly activity.
It can’t be logical because it is based on bad facts.
We wrote evals in August. Anybody racing to get things launched before perf did so months ago. The timing described in the top post is just false.
We write the next one in February. We are almost exactly half way between perf cycles. Your hunch that this lines up with the end of the year is false.
There were outages around the same time last year. Somebody in the HN thread commented back then that the employees evaluation and promotion window ends around december/eoy, thus more releases are made. https://en.m.wikipedia.org/wiki/Google_services_outages