CI/CD seems to be simple. But let's take a step back, and look at it from a helicopter view. Let's think about the design CI/CD processes for the project, team, even organization. Let's go through ""architecture of CI/CD"". What areas should we cover? How to talk with Stakeholders about CI/CD when we design the backbone of DevOps driven Organization?
DevOps Institute Ambassador. CD.Foundation Ambassador. AWS Community Builder. Engineer, leader, mentor, speaker.
My focus is on CALMS. I am building better understanding of DevOps as driver for the organization. And currently I am leading the DevOps and Cloud Academy at EPAM Systems Poland, where we are shaping new engineers to be professionals.