HN user

Andys

1,795 karma

https://github.com/andys [ my public key: https://keybase.io/andy_snow; my proof: https://keybase.io/andy_snow/sigs/ki9L8r0Gt97fbtpZIwvw4kqxcdzvZKrC0DM-XBxewTU ]

Posts10
Comments1,055
View on HN

I worked in a DC that had multiple redundant chillers on the roof, and multiple redundant coolers on each floor, but the whole building's cooling failed at once when the water lines failed somehow.

They didn't say how, but apparently the pipes between each floor and the roof were not redundant. It took almost 24 hours to fix.

[dead] 6 months ago

I'm surprised that we're circling back to banning things being the answer, when we (the Internet) know that doesn't work long-term.

It seems nice at face value, so it appeases everyone, while being an overly blunt tool used as a political weapon, etc.

Thanks for sharing that.

Presumably if you'd split the elements into 16 shares (one for each CPU), summed with 16 threads, and then summed the lot at the end, then random would be faster than sorted?

Not a lawyer, but why not use opensource as an example? Many successful public e-commerce websites have public schemas and aren't all hacked.

Lesson learned for me though, if you "put a require behind a feature flag", you'll get surprise failures when your staging and test environments are no longer able to properly test what might happen in production. Put the require outside the flag and make the flag wrap the smallest possible part of the feature.

Technically they still exist, you can buy new 8086 machines and 386s with new motherboards and recycled industrial CPUs, etc.

That is the art of photography: the challenge of capturing the emotional context in a way that conveys it to a random viewer, drawing on common elements of culture, nostalgia, etc.