alt Hacker NewsDevOps should be a guiding principle for the organization, not a dedicated role. Every developer (or at least: every team) should be able to
- speak to production users
- ship to production
- monitor and learn from production usage
You don't need "devopsy" skills to do that, rather organizational structures that allow for incremental change. FWIW, deployments could still be a 2005-like upload via FTP, and the benefits of DevOps could still be reaped.
Replies
Was that not the OPs point too about it being a sad story and many Devs not being capable of learning to run software outside of an IDE?
So jack of all trades master of none?
We’re seeing the same thing with QA. I guess developers can QA their own deliverables.
Leaving out the key fact that the vast majority of developers have no interest in testing stuff. And thus you end up “testing in prod” like with Microsoft projects.
It’s not a coincidence Microsoft’s software quality has collapsed since they’ve eliminated dedicated QA/SDET roles.
> DevOps should be a guiding principle for the organization, not a dedicated role
The way I've always phrased it is that if a company has "DevOps" teams or titles, they're not doing DevOps by definition