If your business relies on an MSP or SI to run your SDLC and release cycles, you are doing it wrong. #DOES18
The MSP and SI have an incentive to artificially limit the amount of changes you can push in any environment, and then up charge based on the number of (totally artificial) allocated build / deploys per month.
Why would anyone want to be beholden to managed services running the change process inside your business....when it can be fully automated?
{narrator voice}: the MSP and SI are not aligned to YOUR operational objectives.
#DOES18
{narrator voice}: the MSP and SI are not aligned to YOUR operational objectives.
#DOES18
The MSP and SI model is focused on two things 1.) burn rate on allotted hours 2.) billable hours to MANUALLY push change in all your environments. This model helped save a ton of money after the Great Recession, but it absolutely sucks for work in 2018. #DOES18
Everyone in this #DevOps market is fighting the intransigence of models that worked in the mid aughts. I've literally had conversations with CIOs saying, "I can save you three quarters of a fully loaded resource's time."
The response, "we aren't ready to automate because we run 24x7" SMDH, Me: "You can build / deploy anytime. No downtime." CIO, "we're not comfortable with anything that could break Prod."
Run manual forever, FTW!!!
We need to get better in articulating what automation does.
Run manual forever, FTW!!!
We need to get better in articulating what automation does.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
