Un:Think Lightning Talk - Automate or Die
•
0 recomendaciones•192 vistas
Martin Rasmussen talks about how once upon a time there was a bank - and the challenges of automation, and the need for it.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (12)
Destacado
Destacado (13)
Similar a Un:Think Lightning Talk - Automate or Die
Similar a Un:Think Lightning Talk - Automate or Die (20)
Último
Último (20)
Un:Think Lightning Talk - Automate or Die
- 2. ONCE UPON A TIME THERE WAS A BANK
- 4. THEN THERE WERE COMPUTERS
- 7. TIME PASSES AND AN INDUSTRY IS BUILT Large companies everywhere build IT solutions to support the business Complex business solutions Long development time Long time to market Long time to value Kings of complexity In addition to the programmers the emergence of IT towers. More on towers later on.
- 9. BENEFITS Much lower cost, but where did all the programmers go? Much faster time to market and value Democratized IT Business Agility Sounds familiar?
- 10. BUILD TOWERS Mainframe Midrange x86 tower (!= BCS) Networking Storage Tower (2?) End User Tower Support organization Service development
- 11. THE BUSINESS OF INFRASTRUCTURE Life of it’s own with career path and professional bodies Formalized relationship to business Cost center The new Kings of complexity
- 12. AND THE BANK…… All they ever wanted was an App
- 13. Technology People 1950 60 70 80 90 0 10 20 CostlowtoHigh Cost development Technology/Infrastructure vs People
- 15. THE NEXT DISRUPTER Server for less than $5 per month. Western Pay ~ 60,000 servers per Admin Off Shore Pay ~ 30,000 servers per Admin Time to market = very fast Time to Value = very fast IT is a tool for the business constrained by imagination only.
- 17. Technology People People Off Shore 1950 60 70 80 90 0 10 20 CostlowtoHigh Cost development Technology vs People
- 19. Change, or Die!
Notas del editor
- The bank did their business on paper, and here is their marvelous piece of technology
- Then came the advent of Computers and the bank went to IBM and said, We need an App. IBM complied..
- The bank were a bit surprised to learn the needed so much stuff to run their app. They needed new buildings, they needed people, and all of this just to keep the app running
- Then they needed to change the app, and IBM charged very high rates so they had to hire their own developers to write the code for the changes
- The process of building and changing these apps was hard and ardous with very long cycles. The developers and their ecosystem of PMs and Business Managers were the kings of complexity Let’s stick with the software for a bit, because the next thing that happens is a massive big disruption. From the well known commoditiser and budget software company…
- Exactly SAP. Hard to get my head around considering the cost of their solutions, but they totally revolutionised software and the also democratised IT solutuons making the available to smaller companies… Closest thing to SFDC in the 80s,,,, SAP
- Now let’s go back to the infrastructure for a bit.
- So what does all this do to the business of infrastructure?
- Infrastructure as code The operator in charge of the Infrastructure code is the new Neo. Karate kicking bullets, etc…
- This is inevitable, and not even Neo can save you…
- Infrastructure as code Put an illustration of how the end ot end stack of hardware and stuff…