nrki
Joined 10 years ago
Joined 10 years ago
Notably missing from the postmortem
I am wondering how state replication works on the backend. The design mentions using crdt and a gossip proto, but I'm not sure what is actually implemented as it is a tad vague. I haven't dug into the code so forgive me if it is obvious or explained elsewhere.
I don't think anyone really understands how intense wildfires can get when fanned by wind. It will destroy almost anything.
See: Black Saturday bushfires, Australia.
> "it really made no difference whether the houses were brick or timber. In fact, with the speed of the fire front some timber houses fared better than brick as it moved too fast for the houses to catch, but the bricks exploded from the sudden change in temperature."
> "When you have a fire front coming through at 800C it'll melt your window seals and aluminum window frames. The glass will fall out then everything is on fire.
Super-enriched Uranium, however _is_ super rare, expensive and desirable.
As opposed to ...
- not handing it over? Prison, then they figure it out anyway.
- handing it to someone else during wartime? Prison or a firing squad, then they figure it out anyway.
So...definitely for larger orgs, where "emergency availability" would be a big red flag, unless one explicitly opted into a (compensated) on call rota.
I guess one can make an exception for very early career, but again this was about setting a 9-5 boundary