4 ms·

Eh, not a big fan of this, but if it's a just a rebrand no big deal I guess. But what happens when if the DevOps concept turns out to be a fad? Visual Studio ha

Eh, not a big fan of this, but if it's a just a rebrand no big deal I guess. But what happens when if the DevOps concept turns out to be a fad? Visual Studio has such a positive and strong brand association among .Net developers it seems a shame to jettison it but I suppose it's necessary as MS is trying to convince other stacks to use the Azure DevOps(VSTS) CI/CD pipelines.

smudgymcscmudge 8y ago
> But what happens when if the DevOps concept turns out to be a fad? Time to re-rebrand
- chrisrpatterson 8y ago
  [PM on the Azure Pipelines team] The primary focus here is making the individual services easier for teams to adopt. Azure pipelines for CI/CD, Azure Boards for planning, etc. Those services support the overall goal of improving your DevOps practices.
  - smudgymcscmudge 8y ago
    I see that this is more than a rebranding and was just commenting with my immediate, fatuous response. I should save fatuous responses for reddit.
    - nogbit 8y ago
      It adds some humor and unfortunately the lack of it can make HN seem like eating burnt toast at times.
partiallypro 8y ago
Just drop the "dev" and call it AzureOps. Still way less confusing than the prior branding.
- jbigelow76 8y ago
  AzureOps has a nice ring to it! With regards to VSTS, I probably just have a soft spot for Visual Studio itself.
  - ethomson 8y ago
    I love Visual Studio, but the product currently known as Azure DevOps (formerly known as VSTS) really has nothing to do with Visual Studio. The name made a lot more sense back in the day when the premier client was actually the Visual Studio IDE. But today, most people interact with Azure DevOps with their browser and too many people think "Visual Studio Team Services" is a web-based IDE. The name change is bittersweet. We've been "Visual Studio <something>" since the first release of our on-premises product, well over a decade ago. But I'm confident about this next phase of Azure DevOps.
    - partiallypro 8y ago
      VSTS naming was a complaint I heard all the way back at Build 2016. Everyone at the Build booth was confused, and even the people manning the booth said the name was confusing. So...it took long enough.

smudgymcscmudge 8y ago

> But what happens when if the DevOps concept turns out to be a fad? Time to re-rebrand

chrisrpatterson 8y ago
[PM on the Azure Pipelines team] The primary focus here is making the individual services easier for teams to adopt. Azure pipelines for CI/CD, Azure Boards for planning, etc. Those services support the overall goal of improving your DevOps practices.
- smudgymcscmudge 8y ago
  I see that this is more than a rebranding and was just commenting with my immediate, fatuous response. I should save fatuous responses for reddit.
  - nogbit 8y ago
    It adds some humor and unfortunately the lack of it can make HN seem like eating burnt toast at times.

partiallypro 8y ago

Just drop the "dev" and call it AzureOps. Still way less confusing than the prior branding.

jbigelow76 8y ago
AzureOps has a nice ring to it! With regards to VSTS, I probably just have a soft spot for Visual Studio itself.
- ethomson 8y ago
  I love Visual Studio, but the product currently known as Azure DevOps (formerly known as VSTS) really has nothing to do with Visual Studio. The name made a lot more sense back in the day when the premier client was actually the Visual Studio IDE. But today, most people interact with Azure DevOps with their browser and too many people think "Visual Studio Team Services" is a web-based IDE. The name change is bittersweet. We've been "Visual Studio <something>" since the first release of our on-premises product, well over a decade ago. But I'm confident about this next phase of Azure DevOps.
  - partiallypro 8y ago
    VSTS naming was a complaint I heard all the way back at Build 2016. Everyone at the Build booth was confused, and even the people manning the booth said the name was confusing. So...it took long enough.