Growing up your CD Endeavours
We've all heard the gospel that Continuous Development (CD) is good for us. Having worked in GLCs, startups and even a short stint at an IB, I've had my fair share of growing and learning pains. The friction between what we as developers can achieve and actually getting our work out there to our customers, is very real. When there is a huge gap between what you think you know about your product, the operating environment in which it lives, what is in your toolbox today, and what is realistically within your means and area of influence to make a change, you are ready to embark on the journey of growth along your own Continuous Delivery milestones. Where am I on the journey of Continuous Development? Why do I care? What hinders my growth? How do I overcome them and grow? These are the questions you will examine after the talk. The goal for this talk is to inspire people struggling or feeling stagnated in their pursuit of CD/DevOps.
More Related Content
Similar to Growing up your CD Endeavours
Similar to Growing up your CD Endeavours (20)
Recently uploaded
Recently uploaded (20)
Growing up your CD Endeavours
- 1. GROWING UP YOUR CD ENDEAVOURS 1
- 2. … CONTINUOUS DELIVERY MATURITY (WHERE ARE YOU?) 2
- 3. … WHY DO YOU CARE? ▸ Why we do what we do? 3
- 4. … WHAT IS CONTINUOUS DELIVERY? ▸ Continuous Delivery is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way. ▸ Queuing theory ▸ Jez Humble book - mid/late 2012 4
- 5. … WHAT MAKES IT HARD? ▸ Conway’s Law: Organisational structure ==> Architecture ▸ Social boundaries of the organisation ▸ Technical / Architecture Recruitment, team roles, career path, etc 5 ▸ Recruitment, team roles, career path, etc
- 6. … FEATURE TEAM ADOPTION MAP
- 7. … FEATURE TEAM ADOPTION MAP
- 8. … HOW TO GROW? ▸ What business problem does your org have as an opportunity for you to use CD techniques to solve today? ▸ What is painful for you as a developer? ▸ Just talk. ▸ Development as knowledge growth. ▸ Learn so you see possibilities that gives you choices.
- 9. … WHAT WE TRIED? ▸ Business opportunity Jul/Aug 2014
- 10. … WHAT WE TRIED? ▸ Initial:
- 11. … WHAT WE TRIED? ▸ Automate:
- 12. … WHAT WE TRIED? ▸ Dockerise:
- 13. … I GOT BITTEN! WHAT DID I LEARN? ▸ Provisioning, Configuration Management, Release Management, Testing - what do I tackle first? ▸ You will have to change your CI pipeline! ▸ Run tests in production mode if possible - you will change the way you write your tests! ▸ Ability to freeze environment where tests was run. Immutable and repeatable! ▸ Speed! Oh & did I forget to clean up after myself?
- 14. … WHAT’S NEXT? ▸ Monitoring -> Feedback from monitoring to feed/drive feature development / bug fix ▸ Scaling the app ▸ docker-compose or kuberbetes? ▸ Cloud Native app packaging and deployment ▸ Helm + draft.sh, ▸ Metaparticle (Brendan Burns) ▸ Pulumi (Joe Duffy) ▸ Telepresence
- 15. … Q&A & AOB ▸ Know your environment, own your environment!
- 16. … GO LEARN SOMETHING ABOUT YOUR PRODUCT OPERATING ENVIRONMENT THAT YOU DON’T ALREADY KNOW TODAY!