A Tale of Two ITs. Tech, Power, Responsibility
Download as PPT, PDF1 like1,044 views
The document discusses the contrasting eras in technology, highlighting the rapid growth and influence of modern tech companies while also warning of the responsibilities and ethical considerations that come with such advancements. Key themes include the rise of open source, cloud computing, and the need for a cultural shift towards accountability and observability in engineering. It emphasizes the importance of fostering small, agile teams and reshoring practices to enhance proximity to business needs and user experience.
A Tale of Two ITs. Tech, Power, Responsibility
- 1. A Tale of Two ITs: Tech, Power, Responsibility James Governor RedMonk co-founder.
- 2. @monkchips
- 3. It was the best of times, it was the worst of times, it was the age of wisdom, it was the age of foolishness, it was the epoch of belief, it was the epoch of incredulity, it was the season of Light, it was the season of Darkness, it was the spring of hope, it was the winter of despair, we had everything before us, we had nothing before us, we were all going direct to Heaven, we were all going direct the other way—in short, the period was so far like the present period, that some of its noisiest authorities insisted on its being received, for good or for evil, in the superlative degree of comparison only.
- 7. It was the best of times
- 9. 2012: $1bn, 13 employees
- 10. 2014: $19bn, 55 employees, 1m new registered users per day
- 15. new kingmakers
- 18. “Applied science is a discipline of science that applies existing scientific knowledge to develop more practical applications, like technology or inventions.” – Wikipedia
- 21. ci|cd
- 26. service mesh
- 29. deploy!=release
- 31. gitops
- 35. o11y
- 36. just culture
- 45. It was the worst of times
- 52. “Crush humanity out of shape once more, under similar hammers, and it will twist itself into the same tortured forms. Sow the same seed of rapacious licence and oppression over again, and it will surely yield the same fruit according to its kind”
- 55. Container Native is where the puck is going – K8s, K8s, K8s GitOps Observability Progressive Deployment Make Operations and Responsibility pervasive Ethics is your job, just as much as high availability is 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
Editor's Notes
- #3: RedMonk calls practitioners the New Kingmakers. The companies that are succeeding are investing in building engineering competence.
- #8: RedMonk calls practitioners the New Kingmakers. The companies that are succeeding are investing in building engineering competence.
- #15: Which also mean that developer talent is now considered more of a constraint than capital. This is an amazing change.
- #16: RedMonk calls practitioners the New Kingmakers. The companies that are succeeding are investing in building engineering competence.
- #17: RedMonk calls practitioners the New Kingmakers. The companies that are succeeding are investing in building engineering competence.
- #18: 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”
- #19: It is this willingness to open source core IP, which traditionally we would have labelled “competitive advantage”, that defines some of the most successful and innovation companies in the world. Facebook, Netflix, Google. Apple and AWS not so much.
- #20: I talked about becoming a data company. So let’s look at some tech specifics. Here are our programming language rankings – Java, Javascript, Python settled leadership positions. PowerShell and Typescript on the move. Oh yeah – Github uses Rails for a front end, Java for data pipelines
- #21: Some companies are just moving so much faster than others. It’s absurd
- #22: CI/CD is the onramp for everything good in modern software development. Better quality software, built faster.
- #23: 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.
- #24: Kubernetes and cloud native – delivery speed is so hard to get a handle on. The death of LTS
- #26: 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. Crazy fragmentation
- #27: The next big thing, on top of K8s is service mesh, automating configuration, security, policy etc – allowing for sidecarring and routing.
- #28: Or blue green deployments
- #29: But what’s the use case? One is canarying
- #30: 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.
- #31: 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.
- #32: The developer experience – you want to meet the developer where they are. The pull request creates the environments
- #34: But it’s also scary, with an *expectation* of failure
- #35: Debugging in production – needs that kind of automation.
- #36: 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
- #38: All of this stuff can be rather complex though
- #39: 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
- #40: Goes further than AWS lamda however, event triggers across different infrastructures.
- #41: Which brings us neatly to stripe – which has rewritten the rules in terms of service consumability via API
- #42: Autotrader completely rethought its RFP processes after working with Stripe
- #43: 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
- #45: 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.
- #46: RedMonk calls practitioners the New Kingmakers. The companies that are succeeding are investing in building engineering competence.
- #47: So wait – here is whatsapp founder brian acton
- #55: Jump in and learn the new approaches
- #56: concluding