6 ms·
I don't think the trend toward having devs handle all the ops is a good idea. Ops teams, for good reason, tend to be way more conservative than devs. Plus I don
by baus 10y ago
I don't think the trend toward having devs handle all the ops is a good idea. Ops teams, for good reason, tend to be way more conservative than devs. Plus I don't think it is effective to constantly interrupt dev teams with operational issues.
- jamesblonde 10y agoAgreed, but there is definitely a trend towards pushing devs to think more about ops. We internally use chef/kitchen and get devs to run their code on kitchen unit tests before it can be considered ready for a PR. Previously, we only did unit tests, and it's a great improvement. But, yes, the bar is much higher from that to actually running in production.
- djb_hackernews 10y agoThey are conservative because of the ops/dev divide. The constant interruption is a sign of bad ops/dev communication. Unified, the devops have confidence in what they are deploying and actively work to minimize interruptions via automation.
- mentat 10y agoInterrupting them is what pushes them to push quality code not just throw it over to ops and hope for the best. It works quite well with deployment velocities that would shock even normal devops shops.