As someone who's been reading Angry Metal Guy for more than seven years, I hated the decision to use the AI-generated images in this post, too. But don't let that get in the way of the main idea: buy albums on Bandcamp if you can afford it, use Apple Music or Tidal otherwise.
I love his writing too! I read this post a few days ago and really liked it, so I started going through his older posts. It's no coincidence that his writing is good—he's actively working to improve it: https://evanhahn.com/economist-style-guide-book-takeaways/.
I recently re-read this article and can confirm that it's excellent—not just this specific page, but all the other sections under "Garbage Collection" as well.
Thanks for posting this—it's super interesting! I was just curious why the author of the Reddit post didn't publish it on their own blog, since it's definitely worth preserving there.
Great story! Successful cloud performance investigations are always extremely satisfying. I love this conclusion:
It’s a reminder that sometimes performance bottlenecks are hard to diagnose, but with careful debugging, good data, and collaboration with providers, even cloud-level issues can be resolved.
It's sad to see Europe's influence fading, and instead of investing in innovation, politicians are focused on stripping even more freedoms from their citizens.
I've been a Kindle user for over 15 years, but I finally stopped buying Kindle books after Amazon removed the "Download & Transfer via USB" option, effectively eliminating the ability to remove DRM.
I believe that Nespresso measures the amount of caffeine in the final drink, assuming you used the correct serving size. For example, for Ispirazione Napoli (https://www.nespresso.com/tw/en/order/capsules/original/ispi...), they claim that "Per serving of Caffeine is 109mg/25ml".
This article doesn't add much beyond the official incident report, so it's better to just read that directly. Or read this analysis, which at least raises some interesting questions:
The author raised some great questions! But as he admits, they are unlikely to be answered in public, which is why I usually find public retrospectives a bit underwhelming.
Service Control did not have the appropriate randomized exponential backoff implemented to avoid this. It took up to ~2h 40 mins to fully resolve in us-central-1 as we throttled task creation to minimize the impact on the underlying infrastructure and routed traffic to multi-regional databases to reduce the load.
If nothing else, this section of the incident report reminded me of my favorite distributed systems paper: Metastable Failures in Distributed Systems. You should definitely check it out if you haven't already: