[dead]
AWS Fired the One Employee Who Gave a Damn
41–50 of 117 posts
Re: AWS Fired the One Employee Who Gave a Damn
#42I 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…
I get that the writing was a bit over the top.
But the story, my goodness. Giving a damn is such a rare commodity. It makes me sad when companies throw away people with that quality.
I hope that Tarus Balog finds a good spot to land. Here's his LI: https://www.linkedin.com/in/tarusbalog/ if you're in the market for an "Open source wonk. Catalyst. Storyteller. Collector of Memories"
Re: AWS Fired the One Employee Who Gave a Damn
#43Though perhaps a bit long-winded and emotional, it's charming to see something so sincere still in this era.
It's not clear that this individual was fired for being too helpful, but it's been my experience that escalation 2 or more levels to report a problem is always a threat to your career, because it means you're exposing a failure within your management chain.
In this case it went all the way up to the CEO, so it's entirely possible he was mentally marked for "eventual downsizing after enough time to not raise red flags"
(To be clear this is a failure by organizations to protect their own bottom line. By not protecting/rewarding people for calling out systemic they incentivize all sorts of dishonesty by managers and directors which are the rule and not the exception in my experience. Famously there was the amazon case about how long customer support took to answer)
Re: AWS Fired the One Employee Who Gave a Damn
#44A challenging writing style on a really difficult to read page with a sloppy AI header image means that this article was a not a great experience.
[flagged]
The author wanted to thank someone who put real human effort into helping him, and call out Amazon for firing that person and other support staff to replace them with AI.
He decided the right way to do this would be to use AI to generate a post about it.
Personally, the message I get out of this is: "I don't give a damn about others, but others should give a damn about me"
Re: AWS Fired the One Employee Who Gave a Damn
#45[deleted]
Re: AWS Fired the One Employee Who Gave a Damn
#46I 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's style is now overuse of sentence fragments, which this "article" has in spades. Fragments are the new emdash or "delve".
I’ll miss when em dashes were a key giveaway. This generation of LLM has one sure fire tell.
We’ll look back on 2026 AIs fondly.
Re: AWS Fired the One Employee Who Gave a Damn
#47[dead]
Re: AWS Fired the One Employee Who Gave a Damn
#48I 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…
I am so sick of reading this horseshit AI writing. It's like eating vaseline.
Re: AWS Fired the One Employee Who Gave a Damn
#49I 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…
> Some switched to farming. Others opened coffee shops. One bakes bread now. That’s the level of abyss we’re talking about. These are people who know they can’t do anything online anymore. Not because they lack the skills. Because their brains were so filled and indoctrinated with complexity that they found decorating a cookie more fulfilling than maintaining 87 files of Kubernetes manifests plus CloudFormation templates plus Terraform state plus whatever abstraction layer Amazon invented that quarter.
This is a very dramatic way to say "because they got so fucking rich they don't have to anymore"
Re: AWS Fired the One Employee Who Gave a Damn
#50I 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's style is now overuse of sentence fragments, which this "article" has in spades. Fragments are the new emdash or "delve".
Beautiful, lovely sentence fragments. Last I heard, I was on the HN em dash leaderboard, and now sentence fragments?