Azure DevOps (AzDOps? AzDO?)
-
What do you call it? In polite company that is, I've got plenty of other names for it that I can't mention here. Was speaking with a coworker and we got on the subject of Azure DevOps and how neither of us were sure what the proper abbreviation was for it. Both of us were trying to avoid typing the entire thing out each time we were discussing it in an email. ADO is already used, so that's out. AZDops or AzDO sound vaguely scatological. Turns out that I'm not alone (Twitter)[^], glad to see that even Microsoft people have the same problem. I think the best suggestion there would be DevOps for Azure... or DOA.
RJOberg wrote:
Both of us were trying to avoid typing the entire thing out each time we were discussing it in an email
You are discussing the wrong thing (whatever it is) in your emails.
"Coming soon"
-
What do you call it? In polite company that is, I've got plenty of other names for it that I can't mention here. Was speaking with a coworker and we got on the subject of Azure DevOps and how neither of us were sure what the proper abbreviation was for it. Both of us were trying to avoid typing the entire thing out each time we were discussing it in an email. ADO is already used, so that's out. AZDops or AzDO sound vaguely scatological. Turns out that I'm not alone (Twitter)[^], glad to see that even Microsoft people have the same problem. I think the best suggestion there would be DevOps for Azure... or DOA.
RJOberg wrote:
or DOA
Dead Or Alive? Dead On Arrival? :D Why not keep using VSTS? or just DevOps. You could use ADO internally, as I'm sure you're not actually using that term daily, weekly, monthly or even yearly :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
What do you call it? In polite company that is, I've got plenty of other names for it that I can't mention here. Was speaking with a coworker and we got on the subject of Azure DevOps and how neither of us were sure what the proper abbreviation was for it. Both of us were trying to avoid typing the entire thing out each time we were discussing it in an email. ADO is already used, so that's out. AZDops or AzDO sound vaguely scatological. Turns out that I'm not alone (Twitter)[^], glad to see that even Microsoft people have the same problem. I think the best suggestion there would be DevOps for Azure... or DOA.
RJOberg wrote:
I think the best suggestion there would be DevOps for Azure... or DOA.
I only have a signature in order to let @DalekDave follow my posts.
-
What do you call it? In polite company that is, I've got plenty of other names for it that I can't mention here. Was speaking with a coworker and we got on the subject of Azure DevOps and how neither of us were sure what the proper abbreviation was for it. Both of us were trying to avoid typing the entire thing out each time we were discussing it in an email. ADO is already used, so that's out. AZDops or AzDO sound vaguely scatological. Turns out that I'm not alone (Twitter)[^], glad to see that even Microsoft people have the same problem. I think the best suggestion there would be DevOps for Azure... or DOA.
I decided to approach it the same way I approach variable names, and call it what it is: TFS hosted on Microsofts servers.
-
RJOberg wrote:
or DOA
Dead Or Alive? Dead On Arrival? :D Why not keep using VSTS? or just DevOps. You could use ADO internally, as I'm sure you're not actually using that term daily, weekly, monthly or even yearly :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Sander Rossel wrote:
Dead Or Alive? Dead On Arrival? :-D Why not keep using VSTS? or just DevOps. You could use ADO internally, as I'm sure you're not actually using that term daily, weekly, monthly or even yearly :laugh:
* Dead on Arrival ;P * We have a pedantic administrator and easily confused users. We tried using VSTS and kept getting told VSTS was gone and Azure DevOps is the replacement. Same thing occurred when VSO became VSTS. * Can't call it DevOps because then people think we're talking about the DevOps group instead of the product. * Have enough legacy systems that make use of ADO to pull data from Oracle and other DBs that it does come up frequently enough.
-
Sander Rossel wrote:
Dead Or Alive? Dead On Arrival? :-D Why not keep using VSTS? or just DevOps. You could use ADO internally, as I'm sure you're not actually using that term daily, weekly, monthly or even yearly :laugh:
* Dead on Arrival ;P * We have a pedantic administrator and easily confused users. We tried using VSTS and kept getting told VSTS was gone and Azure DevOps is the replacement. Same thing occurred when VSO became VSTS. * Can't call it DevOps because then people think we're talking about the DevOps group instead of the product. * Have enough legacy systems that make use of ADO to pull data from Oracle and other DBs that it does come up frequently enough.
RJOberg wrote:
We have a pedantic administrator and easily confused users
Have you considered more... "extreme measures"? *evil grin* :D
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
RJOberg wrote:
We have a pedantic administrator and easily confused users
Have you considered more... "extreme measures"? *evil grin* :D
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
What do you call it? In polite company that is, I've got plenty of other names for it that I can't mention here. Was speaking with a coworker and we got on the subject of Azure DevOps and how neither of us were sure what the proper abbreviation was for it. Both of us were trying to avoid typing the entire thing out each time we were discussing it in an email. ADO is already used, so that's out. AZDops or AzDO sound vaguely scatological. Turns out that I'm not alone (Twitter)[^], glad to see that even Microsoft people have the same problem. I think the best suggestion there would be DevOps for Azure... or DOA.
Go with ADO. Sure, it's already used, but many acronyms are reused. Meanwhile . . . if when the shyte hits the fan, you have a deniability factory.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
Go with ADO. Sure, it's already used, but many acronyms are reused. Meanwhile . . . if when the shyte hits the fan, you have a deniability factory.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
What do you call it? In polite company that is, I've got plenty of other names for it that I can't mention here. Was speaking with a coworker and we got on the subject of Azure DevOps and how neither of us were sure what the proper abbreviation was for it. Both of us were trying to avoid typing the entire thing out each time we were discussing it in an email. ADO is already used, so that's out. AZDops or AzDO sound vaguely scatological. Turns out that I'm not alone (Twitter)[^], glad to see that even Microsoft people have the same problem. I think the best suggestion there would be DevOps for Azure... or DOA.
Still VSO - no reason to learn new names as we all know what it is and have no room for new names every few months...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
