In the past decade, I've worked across startups and large companies, from datacenter control software and 3D printers to global cloud platforms and big data, from mailing letters and filing taxes to machine learning and research projects. I've taken on roles from hands on development to team building and training to advising leadership on technology and strategy.
I wouldn't recommend doing this on purpose, but if you say something that forces the whole room to stop and consider, you can often break the conversational flow and leave a meeting of managers dead in the water.
You can also do something that wipes an individual manager's mental cache and they'll spend days trying to remember what everyone is up to and what's happening.
I think your final sentence is close, but I'd rephrase it: for managers, those disruptions and conversations in your schedule are them dealing with things that require intense concentration. I think most of them understand what disruption feels like, they just don't associate sitting at the computer typing with that focus because it's not the mechanics of their role -- their focus manifests differently.
My managers only rudely interrupt me when they, themselves, are clearly still processing something their boss said to them and they need my input to unblock that process. Or some kind of thing I need to do now, again to unblock whatever they have going on.
I think you hit the nail on the head, I have definitely experienced a lot of this, even when dealing with managers I enjoy working with and that have an understanding of engineering-type workflows.
I'm not sure "we unilaterally changed the contract without notice and you agreed because you happened to use the product that day" would hold up in any court, for any reason.
A contract requires a "meeting of the minds", which is impossible if one party doesn't even tell the other: you can't agree to a contract you didn't know you were even agreeing to.
I don't believe those terms would hold up anywhere (and this is why sites will tell you, over and over, when the terms and conditions change).
Your number is broken up into 32-bit coefficients to 2^32 as a compounding power (sum over a_i * 2^32i) -- and then you can do it as tensor(ish) operations, if you fiddle with carry/mod steps in between to keep the coefficients the right size and partial results properly aligned.
https://www.linkedin.com/in/michael-gehlke-9010342a3/