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…
AWS Fired the One Employee Who Gave a Damn
51–60 of 117 posts
Re: AWS Fired the One Employee Who Gave a Damn
#52AI writing aside, I still think the author has a point: the customer-centric AWS/Amazon of yesterday is not really there any more, or at least appears in a form that isn't recognisable or useful to every day users.
Re: AWS Fired the One Employee Who Gave a Damn
#53Re: AWS Fired the One Employee Who Gave a Damn
#54I'd probably much rather have read the prompt for this article than whatever this is.
Anyway, I use my `buzzoff.wtf` slop site for this kind of thing. Originally built so I could figure out what startups actually did behind all their buzzword landing pages, but now also to get a summary of articles like this to decide if it's worth reading or not
https://buzzoff.wtf/https://www.seuros.com/blog/aws-fired-th...
Re: AWS Fired the One Employee Who Gave a Damn
#55Re: AWS Fired the One Employee Who Gave a Damn
#56I 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…
Re: AWS Fired the One Employee Who Gave a Damn
#57I 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…
"Not X, not y, not z, A!"
The overly emotional paragraph headlines were also off putting.
Re: AWS Fired the One Employee Who Gave a Damn
#58The trick was always finding the person, but now the elephant has no handlers because all of the people are gradually being removed. It's like all the tech bros watched "The Matrix" thirty years ago and said "What a great business model!"
Re: AWS Fired the One Employee Who Gave a Damn
#59I've mentioned this before, but you want the default to be a dry run and for there to be a --commit, --prod, --for-real, or whatever you want to call it to opt in to the destructive behavior.
Re: AWS Fired the One Employee Who Gave a Damn
#60I 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 templ…
This "author" certainly never baked his own bread or grew his own vegetables. Let alone becoming a professional, which is hard work, probably more hard work than sitting at a desk asking claude to change this or that react component.