E.g., we use PagerDuty, and there's several places, such as routing pages, where I'd just like programmatic control, and code would express much more succinctly the needs of what I want to do than trying to express it through some UI-based "routing" editor thing.
Artifact storage aaS's often come with "cleanup" policies that let you choose between 2-3 different modes of cleanup, mostly wrong one way or another.
In all cases an enumeration of the names of 2-3 fixed functions, when I'd rather pass the function.
---
Since this is posted by the author… you set `.content a { word-break: break-all; }`? Like the name sort of implies, it permits line breaks anywhere, which means that the opening line renders as,
One paper that has been in the back of my mind is for a few years is Efficiently Compil
ing Efficient Query Plans for Modern Hardware1 which details how Tableau's internal
The layout is basically fixed at the containing element's max-width for nearly any width someone might reasonably be using, so outside of font variations, it should basically always render like that (and I don't think font variations would make enough of a difference). (It steps up to a wider width at some point … but that width also lops a word on the opening line.)
Thank you for the styling tip, I'll see what I can do it does look wonky.
Presumably this was meant to read "commutative". IEEE 754 addition and multiplication are commutative (ignoring NaN values), but not associative.