talaketu

Note that Employees were not a party to the merger agreement. Does an acquisition FAQ bind the company? I believe the argument is that it was effectively an offer to employees to stick around, and employees who did so effectively accepted the offer, at the cost of other opportunities in the market, and hence this was a binding contract. This doesn't seem so solid to me.

If "in the park" is meant as an analogy for "on the platform" in content moderation, then curiously enough Twitter suspended @RealDonaldTrump for off-park action (Jan 6).

A wheelchair is used for transporting a person.

Let's say that in your opinion: (a) it's a vehicle, (b) it's in the park, (c) but the park authority doesn't have jurisdiction over the activity.

Is the correct resolution to deny (b)?

Maybe I'm misunderstanding what "in the park" represents within the analogy.

counting grid? What even are these?

Indeed - though I think this is a mathematical philosophy about theories. "Genius" is a nice word choice to emphasize your point - it refers to some kind of distinct spirit that happens to inspire the person, not the person themself. (A little like writing vs typing.)

Business data / process flow is so stable compared to a software implementation that having quality documentation pays dividends again and again. If you could document only one thing, document the business data flow.

Except when update schedule on the client differs from the server.

sure, except obviously sunrise at 6AM and sunset at 6PM.

Yes, this is said, but the meaning of "prove" (which is related to "probe") has not really changed very much at all compared to "test" - a word which in this sense is a metonym from the fired pot used for assay of metal. The meaning in "mathematical proof" or "prove beyond reasonable doubt" or "prove your love" doesn't really diverge significantly from this so-called archaic meaning - a demonstration to show.

On the software abstraction, exceptions are simply a convenient implicit control flow device for handling the alternate path when an intended state cannot be achieved. I don't follow the paper's argument that "current exception design is suboptimal for efficient implementation" - but I would not be surprised considering the lifetime issues.

The primary definition (OED) is "forming an exception", which is why I think this cliche is a tautology ("exceptions are for forming an exception") that does nothing to guide me on whether an exception is appropriate in a given case.

Btw, we don't say "exceptions are for infrequent conditions", because that's not what they're for.

I quite like the etymological "taken out", because it carries a notion of special handling - a control flow aspect that is the main point of using them.

English also has the phrase "the exception proves the rule" - and it's just swell when our general code handles special cases.

I would have not have thought an unreachable host was exceptional, given that it's quite normal.

"exceptions are exceptional" means what?

"round corners feel natural" is no better explanation than "round corners are smoother".