I believe a variant of: "It is a well-known fact that those people who must want to rule people are, ipso facto, those least suited to do it... anyone who is capable of getting themselves made President should on no account be allowed to do the job."
... applies to code reviewers.
I like Google's review standard:
"In general, reviewers should favor approving a [PR] once it is in a state where it definitely improves the overall code health of the system being worked on, even if the [PR] isn’t perfect."
I've been in teams where those comments are never addressed because the pressure is on "push something that roughly solves the task so you can show something during demo".
Azul is popular in low latency financial services. A usecase might be to reduce the variance that JIT compilation introduces to transaction latency, especially at the high percentiles.
There are other things you can't control. Like when NS records for a new domain show up in the servers for the TLD.
I suppose it's reasonable that you could provide a better estimate for new domains and transfers based on past experience and existing TTLs. But it will be an estimate. And the estimates would be individual or sub-group ones, like "estimate for a new .com domain" and "specific estimate for transfer of this domain", etc.
