3 ms·

My recent experience in interviewing candidates is that they have all heard the word "DevOps" but what they understand by it is highly variable, and ranges from

My recent experience in interviewing candidates is that they have all heard the word "DevOps" but what they understand by it is highly variable, and ranges from from a way of working, to a build pipeline in Azure to ... yup, a renamed Ops team. It's pretty sad.

SideburnsOfDoom 7y ago
> some build pipelines in Azure Azure Devops Services: https://azure.microsoft.com/en-gb/services/devops/ https://azure.microsoft.com/en-gb/services/devops/ Since there can't be a successful software delivery method that doesn't involve releasing software, the act of releasing software _cannot_ be new and unique to "DevOps". IMO the new factor is in closing the feedback loop with the final link from live Operations back to Development, therefor if part of your cloud stack _must_ be singled out as the "DevOps" part, it's probably the logging / metrics / observability / alerting piece that does this, and not the good old CI and deploy pipelines.
user5994461 7y ago
It's a pretty good progression from before. The most common name used to be sysadmin. That could be development or operations or anything down to running a Windows Active Directory or HelpDesk. At least with DevOps, there is no doubt that it's about Linux systems and automation.
- SideburnsOfDoom 7y ago
  > At least with DevOps, there is no doubt that it's about Linux systems and automation. Is that what you understand by the term "Devops" ? That "it's about Linux systems" ? Really?? That definition is a new one on me, and you very much should doubt it since "it's about Linux systems" is neither necessary nor sufficient. The confusion is even worse than I thought.
  - user5994461 7y ago
    Are you trying a joke on Linux vs Unix? in reference to companies using Solaris or FreeBSD maybe? (there aren't many left of those). All the DevOps roles I've ever seen are Unix based. In my experience sysadmin roles were more likely to be a windows administration or a helpdesk role than that. I think it's pretty good devops got split into a distinct title. It's not a great experience walking into a sysadmin interview only to find out they are looking for an exchange administrator.
    - SideburnsOfDoom 7y ago
      > Are you trying a joke on Linux vs Unix? No, I'm saying the the DevOps ideas have nothing to do with OS choice. You could use them in linux or Windows or in any other OS; or you could ignore them in linux or Windows or any other OS.
- will4274 7y ago
  > At least with DevOps, there is no doubt that it's about Linux systems and automation. Windows Server still exists and maintains some market share. Automated, continuous delivery, and monitoring of web applications to Windows Server machines is DevOps in the exact same sense that it is with Linux machines. The essence of DevOps is that there's no fence. The same team that writes the code deploys and monitors it. This essence remains unchanged regardless of the hosting platform - Linux, Windows, or even proprietary platforms like AWS lambda.

SideburnsOfDoom 7y ago

> some build pipelines in Azure Azure Devops Services: https://azure.microsoft.com/en-gb/services/devops/ https://azure.microsoft.com/en-gb/services/devops/ Since there can't be a successful software delivery method that doesn't involve releasing software, the act of releasing software _cannot_ be new and unique to "DevOps". IMO the new factor is in closing the feedback loop with the final link from live Operations back to Development, therefor if part of your cloud stack _must_ be singled out as the "DevOps" part, it's probably the logging / metrics / observability / alerting piece that does this, and not the good old CI and deploy pipelines.

user5994461 7y ago

It's a pretty good progression from before. The most common name used to be sysadmin. That could be development or operations or anything down to running a Windows Active Directory or HelpDesk. At least with DevOps, there is no doubt that it's about Linux systems and automation.

SideburnsOfDoom 7y ago
> At least with DevOps, there is no doubt that it's about Linux systems and automation. Is that what you understand by the term "Devops" ? That "it's about Linux systems" ? Really?? That definition is a new one on me, and you very much should doubt it since "it's about Linux systems" is neither necessary nor sufficient. The confusion is even worse than I thought.
- user5994461 7y ago
  Are you trying a joke on Linux vs Unix? in reference to companies using Solaris or FreeBSD maybe? (there aren't many left of those). All the DevOps roles I've ever seen are Unix based. In my experience sysadmin roles were more likely to be a windows administration or a helpdesk role than that. I think it's pretty good devops got split into a distinct title. It's not a great experience walking into a sysadmin interview only to find out they are looking for an exchange administrator.
  - SideburnsOfDoom 7y ago
    > Are you trying a joke on Linux vs Unix? No, I'm saying the the DevOps ideas have nothing to do with OS choice. You could use them in linux or Windows or in any other OS; or you could ignore them in linux or Windows or any other OS.
will4274 7y ago
> At least with DevOps, there is no doubt that it's about Linux systems and automation. Windows Server still exists and maintains some market share. Automated, continuous delivery, and monitoring of web applications to Windows Server machines is DevOps in the exact same sense that it is with Linux machines. The essence of DevOps is that there's no fence. The same team that writes the code deploys and monitors it. This essence remains unchanged regardless of the hosting platform - Linux, Windows, or even proprietary platforms like AWS lambda.