The Transition from Product to Infrastructure

The evolution of software delivery

Transcript

1. The Transition from Product to Infrastructure Paul Stack http://twitter.com/stack72 mail: paul@paulstack.co.uk The evolution of Software Delivery
2. About Me Infrastructure Engineer Reformed ASP.NET / C# Developer DevOps Extremist Conference Junkie
3. Being a software engineer is easy*
4. 1. Someone has an idea
5. 2. Requirements are gathered
6. 3. Development happens
7. 4. Testing / Feedback happens
8. 99. The software is deprecated
9. ALL SOFTWARE has a should have a lifespan
10. The creation of software is only the beginning…
11. “Until your pretty code is in production, making money, or doing whatever it does, you’ve just wasted your time” Chris Read @cread #LondonCI
12. How does code get to your users?
13. Delivery isn’t the #1 priority of the average developer
14. “How long would it take your organisation to deploy a change that involved just one single line of code? Do you do this on a repeatable, reliable basis?” Implementing Lean Software Development Mary Poppendieck
15. Value Stream Map
16. Has anyone read this book?
17. Continuous Delivery …. is a set of practices and principles aimed at, building, testing and releasing software faster and more frequently.
18. Why do we have a problem releasing our software?
19. 1. Continuous Delivery is something only startups can achieve
20. 2. Continuous Delivery only works for NodeJS / Ruby / Go developers
21. 3. We can hire a consultant to help us implement ‘Continuous Delivery’
22. 4. Right click and deploy in Visual Studio is continuous delivery
23. 5. Continuous delivery is as simple as hooking github to our Azure account…..
32. Image by John Turner of PaddyPower.com
34. So what does an infrastructure engineer do?
35. 1. Provides the ability for development teams self service tools
36. 2. Be an evangelist of getting developers to take ownership of their systems
37. 3. Take responsibility for the health of the entire system
38. This sounds a lot like that DevOps thing I’ve heard of..
39. “DevOps is not about learning each other's job, it's understanding the money is made when software is actually running in production.” Dave Mangot @davemangot
40. We are *all* part of the same team!
41. The Benefits of Continuous Delivery • High Performing IT Teams are more Agile! • High Performing IT Teams can recover faster! • High Performing IT Teams can experiment more! https://puppetlabs.com/sites/default/files/2014-state-of-devops-report.pdf
42. I work in a Windows environment, can I take advantage of these practices?
43. Further Reading
44. Paul Stack @stack72