Earlier quoted context omitted.
When I was working at a pretty big IT provider in the electronic banking sector, we (management and senior devs) made it an unspoken rule, that: - Juniors shall also handle production deployments regularly. - A senior person is always on call (even if only unofficially / off the clock). - Junior devs are never blamed for fuckups, irrespective of the damage they caused. That was the only way to help people develop rou…
Same thing -- used to work at a very large hosting provider. One of our big internal infra management teams wouldn't consider newhires fully "part of the team" until they had caused a significant outage. It was genuinely a right of passage, as one person put it, "to cause a measurable part of the internet to disappear". I got to see a lot of people pass through this right of passage, and it was always fun to watch. E…
Google outage – resolved
821–830 of 870 posts
Re: Google outage – resolved
#822Given the blast radius of this (all regions appear to be impacted) along with the fact that services that don't rely on auth are working as normal, it must be a global authN/Z issue. I do not envy Google engineers right now.
Re: Google outage – resolved
#823Earlier quoted context omitted.
> I do not envy Google engineers right now. A few years ago I released a bug in production that prevented users from logging into our desktop app. It affected about ~1k users before we found out and rolled back the release. I still remember a very cold feeling in my belly, barely could sleep that night. It is difficult to imagine what the people responsible for this are feeling right now.
Several years back when I was working at Google I made a mistake that caused some of the special results in the knowledge cards to become unclickable for a small subset of queries for about an hour. As part of the postmortem I had to calculate how many people likely tried to interact with it while it was broken. It was a lot and really made me realize the magnitude of an otherwise seemingly small production failure.…
Re: Google outage – resolved
#824If you pay for Google Services, they have an SLA (service level agreement) of 99.9% [1]. If their services are down more than 43 minutes this month[2], you can request “free days” of usage. Edit: Services were down from ~12:55pm to ~1:52pm, it's 57minutes. Thanks hiby007 [1] https://workspace.google.com/intl/en/terms/sla.html [2] https://en.wikipedia.org/wiki/High_availability#Percentage_c...
Your nines or their nines? I bet if you personally can't use it, but their overall reliability meets the bar, then they're within SLA. Don't ask why I know this.
Re: Google outage – resolved
#825On reddit thread there are some really good jokes about this [1] related to their asinine interview questions. Like: > Did they try to fix them by inverting a binary tree? >> Yeah maybe implementing a quick LRU cache on the nearest whiteboard will help them out here >> Did they try checking what shape their manhole cover is? >> Dev ops was too busy out counting all the street lights in the United States [1] https://w…
Every time I see complaints like this I can't help but think the posters have a chip on their shoulder from being rejected by Google or a similarly selective company. It's never a commentary on any fundamental issues with these types of interview questions and no one ever comes up with a better process that is equally scaleable and effective for hiring generalists. In my experience interviewing with dozens of small, medium and large companies, the vast majority of technical roles require these types of questions now. These come off as criticisms against Google specifically for asking hard variants of these questions.
I don't personally have any issue with companies asking questions like these as long as they don't simply look for "a correct and optimal solution coded up perfectly whilst under stress in under 30 minutes", but rather the process of solving the problem.
Re: Google outage – resolved
#826Earlier quoted context omitted.
None of these are asked in G interviews. The commenters are asinine.
No? https://twitter.com/mxcl/status/608682016205344768?lang=en
Max himself later opened up[0] and admitted to being difficult to work with. It is entirely likely that he was rejected based on his personality and not his ability. As someone who contributed to Homebrew many years ago I would not be surprised if this was the case. In their own words: "I am often a dick, I am often difficult, I often don’t know computer science". I am not sure why any company would want to hire someone like that and put the culture of the team in jeopardy.
[0] - https://www.quora.com/Whats-the-logic-behind-Google-rejectin...
Re: Google outage – resolved
#827Gmail said my account was "temporarily" unavailable... had a moment considering if it wasn't temporary. Good reminder to remove my reliance on gmail especially.
Thunderbird prompting me to login, and getting "Google does not recognize this email address" as a reply was a nice adrenaline spike, until I checked the status on HN!
Re: Google outage – resolved
#828Earlier quoted context omitted.
Why not? (I think I can find some cases where production access from an engineer's workstation is a good idea)
It can be efficient, particularly in smaller companies, but that's where exactly this rule should be applied. In some industries, security and customer requirements will at times mandate that developer workstations have no access to production. Deployments must even be carried out using different accounts than those used to access internal services, for security and auditing purposes. There are of course good reasons…
Re: Google outage – resolved
#829If you pay for Google Services, they have an SLA (service level agreement) of 99.9% [1]. If their services are down more than 43 minutes this month[2], you can request “free days” of usage. Edit: Services were down from ~12:55pm to ~1:52pm, it's 57minutes. Thanks hiby007 [1] https://workspace.google.com/intl/en/terms/sla.html [2] https://en.wikipedia.org/wiki/High_availability#Percentage_c...
https://techcrunch.com/2020/12/14/gmail-youtube-google-docs-...