Download to read offline
Uploaded byJames Governor
The Quickening at Futurestack 2018
The document discusses trends in software development and engineering culture, emphasizing the importance of open source, cloud technologies, and collaborative coding practices. It advocates for smaller teams, progressive delivery, and the necessity of reshaping procurement and training investments. The author urges a shift towards closer user engagement and cultivating a robust engineering culture.
More Related Content
![Vibe Coding vs. Spec-Driven Development [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/vibecodingvsspecdrivendevelopment-251209105622-43f455e7-thumbnail.jpg?width=640&height=640&fit=bounds)
The Quickening at Futurestack 2018
- 1. The Quickening: FutureStack 2018 JamesGovernor @monkchips co-founder.
- 3.
- 4.
- 6.
- 8.
- 9.
- 10.
- 12.
- 15.
- 16.
- 19.
- 20.
- 21.
- 32. Create path findingteams Make open source contributions Container Native is where the puck is going GitOps Observability Make Operations and Responsibility pervasive Refactor for services Break down large teams into small teams, loosely joined Reshoring is a thing. Close to the Business. Close to the User Rebuild engineering culture and competence Rethink procurement Invest in people and training (but not everyone will make it)
Editor's Notes
- #3 Everything is accelerating, and the stakes are higher than ever. Economies becoming more winner takes all. “There can be only one”
- #4 RedMonk calls practitioners the New Kingmakers. The companies that are succeeding are investing in building engineering competence.
- #5 The underlying factors driving the rise of the New Kingmakers
- #6 Which also mean that developer talent is now considered more of a constraint than capital. This is an amazing change.
- #7 We are told we all need to become software companies, but it’s hard to be a software company. Data and services are what people want to pay for – “the software paradox”
- #8 Some companies are just moving so much faster than others. It’s absurd
- #9 Ci/CD is the onramp for everything good in modern software development. Better quality software, built faster.
- #10 CI/CD drove the rise of Docker – the disposable infrastructure approach mapped really well to automated testing (unit, functional etc)
- #11 But Kubernetes emerged as the orchestration environment of choice. Ops people bought into the model, and now it’s the defacto standard for all container-based workloads. All major players have adopted it, including Pivotal, Rancher, Mesosphere, VMware, Microsoft, IBM. And of course Docker itself.
- #12 We’re seeing the whole stack being rewritten and rebuilt on top of K8s, including everything from networking to storage. Unlike OpenStack, K8s didn’t begin with this as a goal, but it’s happening.
- #13 The next big thing, on top of K8s is service mesh, automating configuration, security, policy etc – allowing for sidecarring and routing.
- #14 But what’s the use case? One is canarying
- #15 Or blue green deployments
- #16 CI/CD perhaps doesn’t go far enough – Progressive Delivery is what I call the new routing approaches, with feature flags, canarying etc. taking full advantage of container native cloud infrastructures.
- #17 How developers work – why not do everything through Github? Git for declarative infrastructure, managed deployment by K8s. Pull Request as the unit of work and collaboration.
- #18 Debugging in production – needs that kind of automation.
- #19 But it’s also scary, with an *expectation* of failure
- #20 So along comes observability, beyond monitoring. It’s tracing, logging and monitoring, with real time visibility. A shift of perspective – the developer writes code for it to be understood. It’s as important a responsibility as anything in the testing tool chain
- #22 All of this stuff can be rather complex though
- #23 Which has driven serverless approaches. Easy – no need to think about all the K8s stuff in building stateless apps. It’s 12 factor, totally opinionated
- #24 Goes further than AWS lamda however, event triggers across different infrastructures.
- #25 Which brings us neatly to stripe – which has rewritten the rules in terms of service consumability via API
- #26 Autotrader completely rethought its RFP processes after working with Stripe
- #27 Target has invested heavily in people, from 30/70 internal/consultants to 80/20 internal/external, hiring 1000 people in 3 years. Open source agile skills. Also training third parties. The best way to learn is to teach. Open sourcing. K8s native – every store running Kubernetes
- #28 Allstate created Kompozed labs, teaching agile, improving how it builds software
- #29 Goes K8s Native, dropping Openstack, being more explicit about the new basket of container native/open source contributions
- #30 It’s not all good news. Absolutely brutal takedown of BA in the FT for not investing in software development. First big breach of the GDPR era, and this story is merciless.
- #31 Jump in and learn the new approaches
- #32 But not everyone will make it
- #33 concluding