I maintain that ".NET" is the single worst brand name to come out of Microsoft. I hope the new dotNet version 5 that is supposed to unify Standard and Core (or leave behind stuff like WebForms) gets a new brand name that doesn't have a period in it.

Of course, knowing Microsoft they will recycle some name so even if it's better the Google Searches will be all screwed up, not knowing if it's the new Brand-X or the old one.

"Azure Dev Ops" is up there too. It turns out searching "Dev Ops" gives a lot of responses not relating to the product. Who could have possibly anticipated that?

Side note, I like ADO. I just hate the name.

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....

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.

> 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.

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.

We almost had Windows .NET Server. I don't know how the Windows Server 2003 name managed to win out, but the world was better for it.