foton1981

To be honest I was very surprised to hear what a cache SRE was working on. It sounded like he had to build all of handling of hardware issues, rack awareness and other basic datacenter stuff himself. Does it mean that every specialized team also had to do it? Why would cache engineer need to know about hardware failures at all, its datacenter team's responsibility to detect and predict issues and shutdown servers gracefully if possible. It should be completely abstracted from cache SRE, like cloud abstracts you from it. Yet he and is team spends years on automation around this stuff using Mesos stack that they probably regret adopting by now. I feel like in this zoomed in case of twitter caches what they were working on is questionable, but the team size seems to be adequate to the task, so my takeaway is that like any older, larger company Twitter accumulated fair amount of tech debt and there is no one to take large scale initiative to eliminate it.

Seriously, who cares about 5ms difference? Or even 25ms. I don't. And Asia is just used to longer latencies. Edge compute became a commodity even before it was born.

I am afraid this article will resurrect shortage even if it ended lately: I never cared about pasta shapes, but now I want bucatini. With 52 hacker news points there goes national stock of bucatini.

Its like bitcoin investment. There won't be any more IPv4 :)

I dont understand how would such highly contagious virus suppress and contain itself if it started in CA months ago. As if Californians have no outbound travel. Impossible scenario.

Damn. If this becomes legal precedent will I be forced to read every page of books I buy?

Looks like Akamai error to me.

What if I disable ntpd a minute before leap second is injected and restart it a minute later?

Mac porn :)

Guys just have too much time...