>Plus assert everything all the time.

This is where static checking comes in. Static tests should fail if it's assumed (and not asserted) that a key exists.

From my experience, much of this comes down to the design of the system: was some state modified prior to an error occurring? If so, can it easily be rolled back? If not, why not?

sounds similar to https://redact.dev/

Shouldn't there be an eventID regardless of type?

It may be useless overhead in a high performance system (e.g. game engine) but is probably mandatory for distributed systems.

I'm not sure. We have distributed systems of this type at $JOB and a correlation ID that is generated on user action and attached to every event in the chain (regardless of service) is plenty. I don't think we've ever needed to look at anything so specifically that a unique event ID for each event would have been helpful.

You also get event IDs "for free" with lots of systems, e.g. Kafka topic/partition/offset is more than sufficient as a unique global ID for later use.

That's diffused thinking!

GL getting in. The interviews are arguably harder than that of FAANG.

The worst "attack" I've ever had was with spaghetti squash. I got the usual: bloating and diarrhea but on a scale I had never experienced before. I felt extremely tired void of any appetite for a couple days after. Really wonder what in it did it for me. Maybe it was a coincidence, or an allergy. Haven't figured it out to this day. Other than that, any enriched flour pretty consistently gives me light bloating.

Unrelated but I found this paragraph in the article quite... weird. Natural juices and vitamins?

>One woman, Sandy Funk, had begun having blackouts at the age of 37, having developed a brain tumor. She got herself onto a diet of natural juices and vitamins, and was able to live for another 18 years, but only after they had removed two thirds of her tumor via a surgery.

Same for me. Though I’m 50/50 on this being a deadpan joke, especially after the last part.