I've recently joined a small medtech company as a DevOps engineer, making me the third person in this role. Our main focus is improving our apps and implementing best practices like Infrastructure as Code (IaC) and Continuous Integration/Continuous Deployment (CI/CD). We've got a supportive ops team, but unfortunately, the developers are resistant to change. We currently rely on manual deployments and are just starting to implement VLANS. Every time we suggest improvements, like moving to a Nexus proxy for package management, the developers tend to ignore us and continue accessing packages directly. They also push back on using immutable Docker tags, claiming it's difficult to manage versions in a shared development environment. I'm looking for advice on how to handle this situation effectively, especially since we're not a traditional IT company, and there seems to be little support from upper management despite past incidents that called for better infrastructure.
5 Answers
It might be time to have a serious talk with management about culture and hiring practices. If the devs are resistant to standard practices like versioning, this might signal deeper issues that need attention. Having leadership support in enforcing necessary changes could be crucial for moving forward.
Communication is key. Try to approach the devs not just with what you want to implement but show them why it's beneficial. Explain how the changes can solve existing problems they face daily. Building trust and collaborating is important so they see you as a teammate rather than someone imposing changes on them.
Absolutely agree! If you work in silos, it won’t help. Getting them to trust you is essential. Explain your intent and how it streamlines their work. If they see it's about improving their experience, they’re more likely to listen!
You might want to consider bringing in a qualified developer who can actually advocate for this vision. If the initiative seems to come solely from Ops, it can feel one-sided to the developers. This resistance often points to deeper issues in the team's motivation to innovate. Getting someone on board who understands and believes in these changes can catalyze a big shift in the team’s mindset.
You can also focus on making the right solutions easier to use. Sometimes it’s about shifting the mindset; if you can demonstrate tangible improvements through the right processes, developers are more likely to adopt them voluntarily. Start small with manageable changes and build from there.
That's great advice! I've seen success by working on projects that benefit everyone. If the changes make their lives easier, they’ll come around.
For sure! Make their high pain points your priority. If you can alleviate some of their biggest frustrations, they’ll start to view your suggestions in a more positive light.
Lastly, remember to treat the devs like your customers. Find out what their actual pain points are and cater to those needs with your proposals. If you can automate annoying tasks and improve their overall experience, they’ll be much more willing to listen to your ideas for change.
Yes! Focusing on making their work easier is the heart of effective DevOps. It’s all about finding solutions that enable them, not just enforcing rules.
Absolutely! If you show genuine interest in their struggles and prioritize solutions that benefit them, you’ll find them more open to your suggestions.
Starting with a roadmap showing the strategic objectives of your proposals can really help. Clearly document problem statements, and prioritize them. If you can demo these improvements, that often gets buy-in from the higher-ups too.