Alexis Janero Moliner’s Post

To all DevOps: stop chasing certifications and start chasing "Friction." If you want quick wins in a new role, don’t look at the infrastructure first. Look at the people. Shadow your PMs, ask them: "What part of the release cycle keeps you up at night?" If they’re good, they’ll give you a list of bottlenecks immediately. These aren't just complaints; they are your roadmap for automation. Lead the Developers: they are paid to solve business problems and ship features. They usually don't want to spend 2 hours debugging a YAML file. Don’t ask them how they want the CI/CD to work. Tell them. Provide a well-thought-out, simple, and effective structure. If it works and stays out of their way, they will embrace it. It's not too difficult to tame the "Senior's Pushback", they aren't resisting change because they’re mean; they’re resisting because they’ve seen "new processes" break things before. The fix: documentation + proof. A dead-simple, step-by-step guide is more powerful than a 30-minute meeting. Show them the working solution, and the resistance disappears. DevOps is 20% tools and 80% empathy. Build for the humans, don't be afraid of their feedback, and the systems will follow. That's what I've learned through out my career. Communication is the corner stone of DevOps, not automation. #DevOps #SoftwareEngineering #Automation

The topic of friction is interesting. We often focus on creating automations, but a significant part of our work is creating automations for developers and delivering those automations for them to use. Since DevOps itself prioritizes constant automation, it must consider how to eliminate friction and generate developer-oriented solutions. Undoubtedly, platform engineers are unique in offering developers greater flexibility to perform actions and work faster. Some examples include: - Creating CI/CD and explaining to developers how to use and improve them with everyday tasks not currently included in the CI/CD. - Configuring Dockerfiles to ensure they are secure, small, efficient, and easily integrated with the deployment. In these cases, developers should have basic knowledge of CI/CD and Docker, but without a doubt, DevOps engineers are specialized in infrastructure and are the ones who will be able to do the best work with these technologies.

Angel ILIEV

Founder @ KloudFluent | Principal Azure Integration & DevOps Architect

1mo

Some very valid points. Very good take in my opinion, great insights Thanks for sharing.

See more comments

To view or add a comment, sign in

Explore content categories