AWS Cognito is having issues and health dashboards are still green

Post by jugg1es » Thu, Nov 26, 2020, 4:34 AM UTC

jschwartzi wrote: post #292

owenmarshall wrote: post #285

Earlier quoted context omitted.

> for many companies its a formal warning that you need to shape up or you're going to be let go. Patently incorrect. A PIP is management telling you that you need to seek alternative employment, now . Joking/sarcasm aside: I’ve never seen or heard someone who is placed on a PIP successfully “exit” the PIP. They exit the company or they’re exited from the company. PIPs seem to mark the start of the “we are building f…

I got PIP'ed and actually fixed the problem I had and resolved the PIP. The problem was that I would mis-ship items sometimes in a warehouse. I figured out that I couldn't reliably read some of the product labels, so I went to go get an eye exam. Apparently I had 20/100 vision in one eye due to astigmatism. Getting glasses meant that I quit fucking up, so they dropped the PIP and moved me into another part of the com…

Post by MR4D » Thu, Nov 26, 2020, 4:53 AM UTC

Post by AmericanChopper » Thu, Nov 26, 2020, 5:02 AM UTC

Frost1x wrote: post #321

reaperducer wrote: post #311

Earlier quoted context omitted.

All I see in your response is, "We don't want to tell the truth because it might cost us money." Maybe if it started costing the company actual money, it might make the investments necessary to ensure it doesn't go down in the first place.

Oh, what a pipedream. If only capitalism worked how it was described in textbooks. It turns out there are much easier lower cost optimizations businesses can perform based on managing perception rather than worrying about pesky concepts like utility.

Post by cbkeller » Thu, Nov 26, 2020, 5:23 AM UTC

martamorena9182 wrote: post #287

alfalfasprout wrote: post #266

Earlier quoted context omitted.

It's funny that you point to that as the problem. The problem is more AWS' toxic engineering culture that has engineers fearing for their jobs in a way that guides their decision making. It's bad company culture, end of story.

AWS is big. Amazon is even bigger. Disgruntled people are the ones who often cry the loudest. Just because there may be teams who act like this, doesn't mean that is the case in general. You don't hear a lot of people praising AWS, the same way you don't hear a lot of people saying how great it is to have an iPhone. If I am happy, I have little incentive to post about it, since that should be the default state. But t…

Post by PKop » Thu, Nov 26, 2020, 6:38 AM UTC

mypalmike wrote: post #254

PKop wrote: post #237

Earlier quoted context omitted.

This isn't a question of knowing a service is down. We're assuming the team that is fixing the service, knows it is down. It was a question of not having the resources to direct literally any other person in the org to log into an admin panel and flip a toggle from green to red.

I was merely addressing the "thousands of employees" non sequitur. Org structure means that the raw number of employees is a meaningless metric. The only people who are going to potentially flip that switch are going to have some sort of direct responsibility for the product. That number is going to be very similar whether it's a large company like Amazon or a smaller one like, say, Heroku or Dreamhost.