this post was submitted on 02 Aug 2025
364 points (97.2% liked)
Programming
21948 readers
959 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The author is an egotistical moron and you should save your time and avoid reading this article. As clearly nobody in the comments has. They just devolve into crying about how important they are, admit heaps of fault and hand wave it as not their problem, and then spout conspiracies about why their account was deleted.
Maybe... just maybe you could have just verified your account in time as you were contractually obligated to do. 3-4 business days with 5 days warning... you're just incompetent no matter how smart all your Ruby friends and "free AWS consulting" makes you feel.
This moron literally tried to insist that the premise wasn't that he put all his eggs in one basket because he had "multi-region replication" and claimed independence from US infrastructure.
News flash: AWS is the same company, and that "multi region replication" is AWS replicating their data, not yours. These are features of their platform that underpin their SLA and SLO contracts they signed with you, not YOUR use.
Sorry but this is bullshit. In no sane world is a 5-day warning a valid precursor to a irrevocable total wipe. People go on vacation. People get sick. This is an stupendously bad take.
Yes this developer did a mistake in trusting AWS like this, but this is still an AWS fault.