4 ms·
A lot of people fail to realize there are large multiplicative factors when the infrastructure team makes other parts of the organization implement a “simple” c
by hedora 7y ago
A lot of people fail to realize there are large multiplicative factors when the infrastructure team makes other parts of the organization implement a “simple” change. In large companies, there might be dozens or hundreds of teams that rely on the infrastructure. If the change requires each team to learn the tool of the month, and make a one line configuration change, it will cost the organization hundreds of developer days to implement. If engineering and release management have to schedule that work to align with business constraints, the change is costing years of people time.
If you’re even further down the rabbit hole, you’ve adopted devops, and are forcing people that actively hate operations stuff to learn obscure in-house operations tools. That, combined with preventing them from doing the work they signed up for, leads to burn out and resignations.
It can get even worse than that. I routinely see all of the above compounded with infra bikeshedding that delays rollouts by months, and results in weeks of work per team. At that point, the organizational damage ends up being many times the budget of the IT department.
So, yeah, IT needs to figure out how to help people be more productive while simultaneously implementing best practices, and it’s hard. I deeply appreciate people that are good at that (and have worked with some).