AWS Fired the One Employee Who Gave a Damn • Hacker News Board

Re: AWS Fired the One Employee Who Gave a Damn

#31

Post by sam1r » Tue, May 26, 2026, 1:34 PM UTC

haburka wrote: 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…

Any business with an aws account should by default pretend like that world revolves them and their company.

Because if aws tanks, they will likely tank.

I pardon the drama. If you were in those shoes and the costs being spent for operating business costs- wouldn’t you be freaking the heck out?

Re: AWS Fired the One Employee Who Gave a Damn

#32

Post by _pdp_ » Tue, May 26, 2026, 1:34 PM UTC

In the age of abundant intelligence the most valuable thing will be human capital - especially those that give a damn.

Re: AWS Fired the One Employee Who Gave a Damn

#33

Post by hilariously » Tue, May 26, 2026, 1:34 PM UTC

jadar wrote: 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.

https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_wha...

Re: AWS Fired the One Employee Who Gave a Damn

#34

Post by BariumBlue » Tue, May 26, 2026, 1:34 PM UTC

Yeah, I think one issue is that AI fundamentally dgaf about you and your code base. They don't have a salary on the line, and from their perspective it's not some project they super care about. I think they're happy to help, and dutiful to orders, but if the business dies in two years because of crap code that's no skin off their back.

Re: AWS Fired the One Employee Who Gave a Damn

#35

Post by schnitzelstoat » Tue, May 26, 2026, 1:34 PM UTC

> that’s not a career pivot. That’s a trauma response.

> he wasn’t being philosophical. He was describing the exact contradiction that made his own job impossible.

Is this written by AI? It has the typical "That's not X. That's Y." phrasing. A bit ironic given the content.

Re: AWS Fired the One Employee Who Gave a Damn

#36

Post by hdndjsbbs » Tue, May 26, 2026, 1:34 PM UTC

It sounds like this employee was on a team whose goal was to build developer goodwill in open source. Of course now that AWS is piling money into the AI furnace they're cutting that team.

This article should be called "the guy who made the best sandwiches in our free staff cafeteria got laid off".

Re: AWS Fired the One Employee Who Gave a Damn

#37

Post by SpaceL10n » Tue, May 26, 2026, 1:35 PM UTC

| When the people who built and operated your cloud would rather knead dough than touch a terminal again, that’s not a career pivot. That’s a trauma response.

Yes it is and I'm glad someone has said it. I didn't realize it until now.

Re: AWS Fired the One Employee Who Gave a Damn

#38

Post by protomikron » Tue, May 26, 2026, 1:35 PM UTC

> Not a X. Not a Y. Not a Z. The thing he was most proud [...]"

This construction - how is it called? It is clear "AI speak" - at least I remember Claude talking like that (even if it is code).

Re: AWS Fired the One Employee Who Gave a Damn

#39

Post by ramblurr » Tue, May 26, 2026, 1:36 PM UTC

Gosh. I am very interested in the story here. But I find that I can't engage with the text, because all my attention is going to is noticing the AI-isms. The way in which a message is delivered matters.

Re: AWS Fired the One Employee Who Gave a Damn

#40

Post by gorjusborg » Tue, May 26, 2026, 1:37 PM UTC

This is what happens to companies who dominate completely; they stop playing the game that they were winning and start playing a different game.

While the article speaks about an individual getting fired from a giant corporate behemoth, all I could think is, most people in the company probably have zero idea who that is.

Big becomes a problem in itself, and you start having to solve the problems of bigness instead of the problems you were solving that made you big.