←back to thread

AWS Lambda Silent Crash – A Platform Failure, Not an Application Bug [pdf]

(lyons-den.com)
115 points nonfamous | 3 comments | 15 Jul 25 01:22 UTC | HN request time: 0s | source
Show context
Analemma_ ◴[15 Jul 25 03:59 UTC] No.44567703[source]▶
This post is a good lesson on humility, and why emotionally-heated blog posts might not be a great idea, no matter how satisfying, and you should possibly stick to dry technicalities instead. If OP had just written up their experience without all the sneering and potshots at Amazon support, people would've just gently corrected them. But as it is they look like a tremendous asshole, and certainly not fit for a CTO role, either temperamentally or skill-wise.
replies(1): >>44567915 #
1. Quarrel ◴[15 Jul 25 04:50 UTC] No.44567915[source]▶
The poor guy has obviously wound himself in knots over this for several months. He went through all this, obviously really bothered by the impersonal Corporation, "solved" his problem by moving to Azure, but then wrote up this massive rant.

Sounds like he needs a holiday at the least.

The mere idea that reddit has a special Amazon protection team that is the cause of his account suspension is ludicrous.

Hopefully this exposure will help him out.

replies(1): >>44604497 #
2. lazystar ◴[18 Jul 25 13:35 UTC] No.44604497[source]▶
> Hopefully this exposure will help him out.

looks lile he took down his site after some other commentators in this discussion noticed some discrepencies in his resume. specifically his claims of having a PhD and a JD. Con men never learn, they just play the next fool.

replies(1): >>44612105 #
3. Quarrel ◴[19 Jul 25 02:43 UTC] No.44612105[source]▶
Wow, missed this.

Yikes.