Microsoft escrow construction metaphors are Microspeak jargon
Over the past few months, we’ve taken a closer look at Microsoft’s confusing vocabulary for internal communications. Forget the usual business jargon; like many organizations, Microsoft has its own set of abbreviations and, sometimes, completely new terms designed to make communication more effective and efficient.
Earlier this month, veteran Microsoft engineer Raymond Chen revealed that the company often uses phrases like fire – “if something has gone terribly wrong and needs immediate attention”.
The product in question will first need to meet several restrictions before it can be declared as such, including surviving a period of joint testing and household use. This is done to ensure that the product meets the specified quality and reliability standards.
“The metaphor is that the property is placed in the hands of a third party to be released to the customers, provided certain requirements are met,” Chen pointed out.
You described it as unhelpful because the blog actually explained the metaphor being used another metaphor. In that sense, Microsoft used baking to explain “(of code switching) to build confidence by looking at its behavior over time.”
The Developer Release Team blog unhelpfully defined escrow as “the stage before the completion of an RTM milestone where the product goes through a period of baking time.”
Microsoft veteran, Raymond Chen
Instead, Chen says the full explanation of the escrow will be “the stage before the completion of the RTM milestone where the product does not accept changes while its behavior is closely monitored to ensure that it meets the release criteria.”
If the release team identifies a problem with the product, they will need to evaluate the situation to determine if it is complex enough to warrant a product change. As part of the testing process, the team will need to find out how often the problem occurs, whether it affects more than one class of users, the severity of its effects, and how easy it would be to find a solution.
“If a sufficiently severe bug is detected, then an escrow reset is declared, and the bug fix is accepted, a new build is generated, the new build is declared as the new escrow build, and the cycle repeats,” added Chen.
The company will have to go through the highlighted process several times until it passes the payment period without escrow events. Therefore, the construction of the escrow proceeds to the production stage.
What do you think of Microsoft jargon?
I would like to know what you think about Microsoft using “escrow builds” as part of its product release cycle. Do you think it has the right effect?
Join us Reddit at r/WindowsCentral to share your information and discuss our latest news, reviews, and more.
