Live data from Hacker News

AWS Fired the One Employee Who Gave a Damn

seuros.com

21–30 of 117 posts

Re: AWS Fired the One Employee Who Gave a Damn

#22
post #4

The massive AI generated image header is more than a little bit ironic

The obviously ai generated dramatic prose. The entire site has the veneer of AI generation as well. The gradient background, the glowing header text, the monospaced fonts, the dots next to the footer subnav items that serve no purpose. If i were writing a blog today i would take comfort knowing it has never been easier to stand out by simply being yourself.

Re: AWS Fired the One Employee Who Gave a Damn

#23
post #13

This piece imputes motives that I feel like is rather impossible to prove. Is it a bad look? Yes. Did it come from malicious intentions / retribution? Unlikely.

I think the lack of motives are part of the argument: that aws management is acting with complete indifference, not out of malice; and that this indifference is leading to the people who actually make a difference being forced out.

Re: AWS Fired the One Employee Who Gave a Damn

#24
post #4

The massive AI generated image header is more than a little bit ironic

The “Question? Answer.” format seems way overused, too. I don’t usually comment on “LLMiness” of blog posts, but here it seems to somewhat devalue the point the author is trying to make.

It is, indeed, heartbreaking to learn that the one person in a giant corporation that cared about your problem enough to pull some strings and fix it gets laid off. But if you truly care about them, why don’t you try and write about it yourself, in your own voice?

Re: AWS Fired the One Employee Who Gave a Damn

#25
post #6

I think this kind of overly dramatic writing makes me struggle to respect the arguments in the piece. Like the blog writer has this style like they’re documenting the collapse of humanity or something when really it’s just a massive cloud company taking some direction that may be suboptimal. I understand this tone can be helpful to drive effective change but I think it should be reserved for situations where people a…

Claude is a bit of a drama queen.

Re: AWS Fired the One Employee Who Gave a Damn

#26

He should not take it personally. Its clear it was a decision by the algo...The AI probably saw "reduced escalations" and concluded he was no longer needed.

The only people or thing to blame for reduction of workforce is leadership/management. F** them.

Re: AWS Fired the One Employee Who Gave a Damn

#27
You know, sometimes corporate America forgets its own principles. You know, Mr. CEO, how you don't really much care why the system went down, you just want it fixed ASAP, no excuses, just get it done?

You know what? We customers are the same way. We don't care why something broke. All we see is that it broke. We are going to take appropriate actions, and you can't stop us.

We don't care that you say it was AI. It was broken.

We don't care that you got lots of cost savings from firing the employees that actually knew what they were doing. It was broken.

We don't care why it broke. It was broken.

Enjoy the window of being able to say "but it was AI" and getting anything from it. It won't last long. We don't care. We don't care for this excuse any more than you're going to accept it from your own employees for much longer.

Re: AWS Fired the One Employee Who Gave a Damn

#29
post #6

I think this kind of overly dramatic writing makes me struggle to respect the arguments in the piece. Like the blog writer has this style like they’re documenting the collapse of humanity or something when really it’s just a massive cloud company taking some direction that may be suboptimal. I understand this tone can be helpful to drive effective change but I think it should be reserved for situations where people a…

If I scroll down and you do animations to the text I am out instantly.
Post reply on HN