The part of Devops that concerns me is the "ops" part. As far as I can tell, it's an excuse for developers to do operations as well. Supposedly, the developers themselves are supposed to be responsible for fixing any problems no matter what time.
My last client was big on devops and applied subtle pressure for everyone to work 24/7, to be ready at any time to respond to a text message and start working. There was never any direct policies laid on by the client, only a subtle pressure that you should do what's neccessary to make yourself indispensible. That was all that was needed for insecure contractors to take it on themselves to work all kind of crazy hours and weekends. It didn't help though, because every contract is ending in Feb because of IR35. No consideration given for all that extra time.
Remember the good old days when the development team had testers who just did testing? And there was an entire operations department who deployed code and stayed up all night to make sure it was running?
My last client was big on devops and applied subtle pressure for everyone to work 24/7, to be ready at any time to respond to a text message and start working. There was never any direct policies laid on by the client, only a subtle pressure that you should do what's neccessary to make yourself indispensible. That was all that was needed for insecure contractors to take it on themselves to work all kind of crazy hours and weekends. It didn't help though, because every contract is ending in Feb because of IR35. No consideration given for all that extra time.
Remember the good old days when the development team had testers who just did testing? And there was an entire operations department who deployed code and stayed up all night to make sure it was running?
Comment