4 ms·
A DevOps position is partially sales role. Telling devs that their well-known and understood scp workflow is bad and instead the should use this tool they don't
by Sebb767 4y ago
A DevOps position is partially sales role. Telling devs that their well-known and understood scp workflow is bad and instead the should use this tool they don't know to look at logs and this completely different tool to deploy the app is bound to fail. If you want to change the way developers work, you need to show them why the new way is better and make the switch as painless as possible. And if you can't do this, you should think hard about why you want them to make that change.
- hedora 4y agoTelling developers to [do the ops team's job, the way the ops team would, assuming the ops people were actually doing their jobs and not just swamping the dev with weird high priority but boring bugs] is an extremely hard sell. I greatly prefer it when the ops team tracks the time they spend on incidents, then stack ranks the ways in which my software sucks (in terms of hours of their time wasted), then asks me to fix it. The same thing goes for $/perf discussions. I don't care if they want to SCP or ftp or send my code over a QUIC tunnel through a bastion host on the moon. If developers have to know there is a new or old way of doing that, then the CI/CD team has failed. If you want me (the dev) to fix CI/CD, then I'll happily reimplement it with make and a fault tolerant NFS share. I'll even explain why that has been the best available approach since ~1985.