asztal

This has happened to me multiple times with AWS SDK V3 (and other packages like react, cassandra-driver, etc.) and while there are ways to avoid it, it's not entirely simple to prevent.

Sadly, the most robust solution is often to use duck typing, e.g. instead of checking if the error is an instance of ResourceNotFoundError, check if error.code equals "ResourceNotFound" which works even if there are multiple library versions present. This is especially the case if you're writing a library that might be provided an instance of an AWS SDK v3 client, as it could be a different version.

I've been doing this stuff for 20 years so I'm used to it, I just feel bad for the novices.

*****? That's amazing! I've got the same password on my luggage!

This looks nice, but would be better if it were fully functional. Maybe it could integrate with http://www.linuxgenuineadvantage.org/?

Kindle has this in eBooks, for English and Chinese. There's 3 or 4 difficulty levels. I'm just hoping they'll add more languages. (Or that there will be a free software solution...)

My first thought was about NetHack. That game is ruthless, and has no qualms about letting the RNG screw you over. If you make 3 attempts at something with a 1 in 3 probability of success, you'd better be prepared for that 29.6% chance of failure.

And don't even talk to me about breaking mirrors...

Didn't expect to see you posting here either. Anyway, thanks for teaching me what a sausage catastrophe is!

Ascended my first tourist yesterday! It's actually a great class to play after the quest. You just have to be very careful (and perhaps lucky) in the early game.

Sounds exactly like my experience doing Project Euler. I learned a lot about mathematics from it. I don't know how much of it actually helped me as a programmer, because I don't tend to run into problems of this nature (not that I notice, anyway), but it was fun.

StartCom is based in Israel as far as I know.

The main thing I am looking forward to becoming accepted is the async/await proposal.

It makes my code look a lot easier to follow, easier to write, and less error-prone.

The company I work for had problems with users who couldn't install our ClickOnce-deployed application. It turned out that they were using a 3G dongle which modified one of the JPEG files in-flight such that it didn't match the hash in the application manifest. We moved to HTTPS anyway so thankfully this stuff is more or less history.

Exactly. It seems perfect for this sort of email because the existing PKI handles trust.