How to survive continuous innovation - Sebastien Goasguen - DevOpsDays Tel Aviv 2017
•
1 like•331 views
DevOpsDays Tel Aviv 2017
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (7)
Similar to How to survive continuous innovation - Sebastien Goasguen - DevOpsDays Tel Aviv 2017
Similar to How to survive continuous innovation - Sebastien Goasguen - DevOpsDays Tel Aviv 2017 (20)
More from DevOpsDays Tel Aviv
More from DevOpsDays Tel Aviv (20)
Recently uploaded
Recently uploaded (20)
How to survive continuous innovation - Sebastien Goasguen - DevOpsDays Tel Aviv 2017
- 1. How to Survive Continuous Innovation ? Sebastien Goasguen @sebgoa
- 4. Thank you
- 11. Later raised $30M C round to “take on VMware”
- 12. Why this software ? How do we find them ? How do we choose ? Why do we adopt them ?
- 13. Trends or fashion ? Euca, Openstack, CloudStack, Kubernetes, Lambda
- 14. Example: “OMG Lambda is killing it, people are going to skip containers and go straight to serverless …and forget about your cloud…”
- 15. GAFA R&D ~ State Budget 2015 data, now ~$100B/y France ~$70B Israel ~$15B
- 16. Observations • Perceived increased pace of software innovation • R&D budgets of corporations is greater than state (theoretical research) • Not a “brain drain”, but a “corporate drain" • Is that a problem ? Another keynote/openspace ? • Expectations that the workforce can keep up with all these new technologies is unrealistic
- 23. IT’s THE FUTURE
- 25. FOMO
- 26. COOL vs NOT COOL
- 28. 0-day Software … put in production Term taken from Kris Buytaert
- 30. Why this Explosion ?
- 31. What happened in 2008 ? Euca, Openstack, CloudStack, Kubernetes, Lambda
- 33. 57M repos, 20M users
- 35. Open Source Now • Every vendor is doing OSS • OSS conferences very vendor driven (except DoD and FOSDEM) • Explosions of tools because we all share (good) • Software go viral thanks to social media echo chambers • Business model for OSS startup is harder • Big corp can cannibalize you
- 36. Remember DevOps
- 39. thanks to Container Solutions
- 40. Principles • Work as a self-organizing team • Empathy between dev and ops, no silos • Deliver value early and continuously • Solve customer’s problems
- 41. Agile Manifesto “ Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan ”
- 42. Remember DevOps •Not here to build cool software •Not here to be hip •Here to provide solutions …while having fun…
- 44. RESEARCH
- 45. 1987, published as annex in 20th anniversary of Mythical Man-Month (1995)
- 46. Software Does Not Come Out of Thin Air
- 49. VMs in Containers ! Source: http://sebgoa.blogspot.ch/2015/05/running-vms-in-docker-containers-via.html
- 50. Write a book
- 51. ADAPT •Does not mean ADOPT •Means: develop a culture of adaptation
- 52. Not only with the business but also with the industry/tools
- 53. Example: Docker • Image provenance and content • Image size • Image security • Tooling (e.g Docker machine, Docker Swarm…) • Who builds your images ? • How are they monitored ? • Where are the logs ?
- 54. Avoid the Stars Syndrome
- 55. Because Software Go Viral too!
- 56. Don’t forget • Build solutions for your business • Develop a culture that adapts to change • Tools will not break your silos • “Stay curious” • Be critical but not a hater, don’t dismiss.