1. 2
  1.  

  2. 4

    You have to lobby people to change their processes and workflow. If you do not put in the legwork into figuring out work out how to make it downhill and simply natural for someone to come over to your side of a fence, you have to be a fool to think you are going to get anything other than a caustic response.

    There is very little appreiation for the history of the environment. There are awkward coworkers, but their awkwardness comes from having seen ‘cowboys’ drive on through their patch and leave them with yet another tire fire to look after as they ride off back into the sunset.

    You are creating someone more work, whether that is in education or raw hours they have to put in, in addition to their usual work hours and remit.

    It is irrelevant if the time investment will save energy down the line, as rarely there is anything but blog posts as evidence to back claims made by the DevOps world.

    How I tackle this with my clients. This whole DevOps stuff is nonsense, I work on persuading them that:

    • People do things as it seems to be the right thing to do, not because they are idiots or asshats
    • If you see a problem, just fix it, let everyone know
    • A deploy needs to take seconds, life is too short to spend five days setting up a test rig and another five days deploying it and no out of hours deploys…don’t you have a family?
    • Get feedback from the deploy in seconds, not days

    No where have I mentioned tooling, it is irrelevant. Whether people adopt hipster orchestration tools or just shell scripts does not matter as if they can deploy in seconds, it is mission accomplished and they can get back to solving the 101 other problems they have.

    Everyone, including the junior dev hired this morning, should be able to confidently do production deploys in a time window that is proportional to the size of the change (3 lines of code…15 mins max end to end).