Re:Why We Terminated Our Partnership with Microsoft
by mikece on Tuesday January 28, 2020 @11:06AM
(#22170618)
I especially hate the name for the on-prem version.
Boss: "Why the [bleep] did you guys put our code out in Azure?" Team: "No, it's on-prem -- TFS is now Azure DevOps." Boss: "Why didn't you tell me that Microsoft was forcing us to move our code to Azure from TFS?" etc....
Re:Why We Terminated Our Partnership with Microsoft
by fernandotakai on Tuesday January 28, 2020 @11:21AM
(#22170779)
microsoft cannot get naming right. and it's not only the azure team, everything microsoft is weirdly named. a good example? the new console is called "xbox one x series". why microsoft.
Re:Why We Terminated Our Partnership with Microsoft
by SideburnsOfDoom on Tuesday January 28, 2020 @11:16AM
(#22170737)
> It turns out searching "Dev Ops" gives a lot of responses not relating to the product.
Good, "DevOps" is a philosophy of moving DEVelopement and OPerations together, operating in production, deploying and monitoring software, not merely a MS product.
Arguably the monitoring and feedback part is more characteristic of "DevOps", because well, any software method that succeeds must involve deploys.
And that's why it's an awful product name for a deploy toolset.
Re:Why We Terminated Our Partnership with Microsoft
by WorldMaker on Tuesday January 28, 2020 @11:24AM
(#22170811)
My favorite naming trouble with Azure DevOps is trying to troubleshoot a project-level issue in Repos or Boards for example and trying to filter out the mostly unrelated Azure DevOps Projects (the almost-but-not-quite CloudFormation-like tool) documentation.
Side note, I like ADO. I just hate the name.