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.
Most rural houses in Australia are built this way. They still burn down.
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.
> Oppie, a scientist at the peak of his field, willingly handed over the most powerful weapon known to humanity to... a person with a less-than-stellar moral code: President Truman
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.
Well, this thread was about setting a boundary of 9-5...would people go to a startup expecting that?
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
Symptom of an organization that doesn't plan and instead of budgeting for 1.3x employees for outside hours support, budgets for ~0.9x and extracts the rest with "expectation".
Our team, led by me and some others, negotiated hard when asked to go on call, that being a material change to our employment contracts at the time.
We ended up with a generous $ stipend per on-call shift, as a % of salary, as well as time off in lieu.
As generous as it sounds, it was an equitable solution in the end, given that we were supporting a multi-million dollar platform that was not fully stable at the time.
A lot has been said by other companies like "your salary should cover that", but I say nuts to that. On-call should be something people actively want to go on. It should be equitable, not forced.