10 Years of DevOps

Article published in LINE engineer blog: https://engineering.linecorp.com/zh-hant/blog/tech-sharing-devops/

DevOps has been for 10 years and are you ready for change?
- MOTIVATION FOR CHANGE
- CULTURE MATTERS
- WHAT CAN WE DO

Transcript

1. 10 Years of DevOps ~ Are you ready for Change?
2. MOTIVATION FOR CHANGE
3. Why Changes? • To follow leaders like Google / FB • New techs are cool, ex: docker, K8s • Copy competitor • New competitor in town • Stay competitive • Arch. needs to scale out • Technical debt, arch. modernization • Throughput, latency, correctness • Velocity & (Cost) Efficiency
4. Competition - IBM, MS v.s. Google
5. Arch. Scale Out - Uber Uber: https://stackshare.io/stack-history-timeline-uber-tech-stack-evolution
6. Velocity & Efficiency - Nokia • Symbian (2010) took a whole 48 hrs to build • Means 2 days later to find out changes work or not • Pipeline cadence & feedback cycle are important • We agree with “The Mythical Man-Month” but that does not apply to high IT performance org. (ex: Google) • DevOps helps scale IT productivity
7. Productivity
8. CULTURE & PROCESS “Culture is how we think, what habits we create and what we do when we're interacting with each other every day.”
9. From Worst to Best Quality picture src: https://www.slideserve.com/ivanbritt/nummi-powerpoint-ppt-presentation story: https://www.slideshare.net/KellyCar/managing-change-lessons-from-the-global-prof-singh
10. Culture Explain • Amazon • 3 big ideas: put customer first, invent and be patient. • Great experience, a legendary kind • Embrace continuous experience improvements • Netflix Culture Deck • Viewed 19,000,000+ times • “The most important document ever to come out of the Valley.” • Freedom & Responsibility • Great teams keep best talent, big salary
11. Culture for IT Engineering Psychological safety • Westrum organizational culture Learning organization • Spotify Engineer Culture
12. Good v.s. Excellent • Ex: Trunk-based development (TBD) • Practice TBD enables team skills like canary release, stage rollout, … Culture for IT Engineering - Conti. Very very few use trunk- based development Elite companies scale well with it New unicorns advertise it Best-selling books promote it Statistic data prove it
13. WHAT CAN WE DO
15. In DevOps, what to Change for RD?
16. • DevOps focus on developer and operations • Testing is absence from the the term • Testing is a pervasive activity throughout development (like the air) In DevOps, What to Change for QA? image: Dan Ashby [https://danashby.co.uk/2016/10/19/continuous- testing- in- devops/]
17. In DevOps, What to Change for OPs? source: CNCF Cloud Native Landscape
18. • Changing might cause failure • No change is the same risk as changing • Do it before too late We are good why still change?
19. Personal Win Company Competitive
20. • Technical Vision - Embrace changes • Growing Technical knowledge - Establish “Chapter & Gild” • Tech Debt Management - Do it early & consciously • From Local to Global Improvement - Advertise it & contribute to community Takeaway ‘We keep improving our culture as we grow. We try to get better at seeking excellence.’’ ~ Netflix culture deck