5 ms·
It might be surprising to outsiders and perhaps it shouldn't spill out, but it's pretty normal lingo inside Google engineering. You turn up things (services, cl
by puzzle 8y ago
It might be surprising to outsiders and perhaps it shouldn't spill out, but it's pretty normal lingo inside Google engineering. You turn up things (services, clusters, products) and later turn them down.
- devoply 8y agoDouble speak at a company that does no evil. Color me surprised. I prefer the verb kill. Google gives life to certain services and then kills them.
- puzzle 8y agoYou are ascribing motives that don't exist. It's not double speak, if you're referring to 1984: it's just that "turning down" is the converse of "turning up". That's a fairly simple and straightforward explanation, no matter how unfortunate it turns out to be. Most of the time, it's used when an internal service moves: it turns up in X and turns down in Y. I'm not sure what your motives are, but I know that you're off mark here.
- aparks517 8y agoIME, it was common lingo in the telecom world a couple decades ago too. Typically in reference to physical circuits.
- joshuamorton 8y agoTo expand on this a bit, it's likely that the etymology here is from SRE-land where they're dealing with turning up the resources for a service, and turn up is very similar to "spinning up", although inclusive of non-HDD resources.
- mc32 8y agoThere is a difference to me in turning down a service (you could turn it up again) and shutting down a service (not going to ever come back up (in the same incarnation.)) Even shuttering a service works.