CTO in a Box
16 likes2,281 views
The document discusses how to adopt a CTO mindset, detailing the differences between this and other roles, and outlines tools for effective thinking. It also emphasizes the importance of risk management and introduces various concepts related to system resilience and architecture. Additionally, it touches on topics like disaster recovery, scalability, and the principle of stigmergy in organizational operations.
CTO in a Box
- 1. @mastermark CTO in a Box Mark Masterson - @mastermark
- 2. @mastermark
- 3. @mastermark
- 4. what will we cover? @mastermark ● How to think like a CTO ● Why (and how) that’s different than thinking like <insert role name here> ● Tools you can use to be more effective and successful in thinking like a CTO ● Some examples of what thinking this way leads to
- 5. @mastermark Karl Marx “Sell a man a fish, he eats for a day, teach a man how to fish, you ruin a wonderful business opportunity.”
- 6. what we won’t cover @mastermark ● Working code ● Working code ● Working code ● and lastly: working code...
- 7. @mastermark Think like a CTO?
- 8. @mastermark
- 9. @mastermark THE MAP IS NOT THE TERRITORY Alfred Korzybski https://en.wikipedia.org/wiki/Map%E2%80%93territory_relation
- 10. @mastermark
- 11. @mastermark
- 12. @mastermark
- 13. @mastermark
- 14. @mastermark
- 16. @mastermark
- 17. @mastermark Scene from Monty Python and the Holy Grail Copyright ® 2000-2009 New Media Broadcasting Company, Inc. All Rights Reserved. http://pythonline. com/
- 19. @mastermark Risk = likelihood (failure) * cost (failure) https://goo.gl/6pjsbu
- 20. @mastermark Risk = likelihood (failure) * cost (failure) FAULT PREVENTION
- 21. @mastermark
- 22. @mastermark
- 23. @mastermark
- 24. @mastermark Risk = likelihood (failure) * cost (failure) FAULT PREVENTION FAULT TOLERANCE
- 25. @mastermark
- 26. @mastermark
- 27. @mastermark Risk = likelihood (failure) * cost (failure) MTTF FAULT TOLERANCE
- 28. @mastermark Risk = likelihood (failure) * cost (failure) MTTF MTTR
- 29. @mastermark
- 30. @mastermark Risk = likelihood (failure) * cost (failure) FAULT PREVENTION FAULT TOLERANCE ROBUST
- 31. @mastermark
- 32. @mastermark Risk = likelihood (failure) * cost (failure) FAULT PREVENTION FAULT TOLERANCE ROBUST ADAPTABLE
- 33. @mastermark
- 35. @mastermark
- 36. @mastermark
- 38. @mastermark
- 39. @mastermark
- 41. @mastermark Buying (storage) assets only makes sense if the asset has a lifetime of greater than 4 years To Lease or Not to Lease from Storage Clouds http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=5445166
- 42. @mastermark
- 43. @mastermark OK. Let’s see some (more) examples
- 44. @mastermark
- 45. @mastermark
- 48. @mastermark
- 49. @mastermark Rethinking Time in Distributed Systems (Stanford, Lec. 6, 2009) https://goo.gl/Pg1ceP
- 50. @mastermark R RESILIENT RUGGED RELIABLE Concepts / features Feedback loops Circuit breakers Limp Mode Degenerate Nodes MTTR Etc. Maps to… Concepts / features Disaster recovery Business continuity Backups Patching Virus scanning Etc. THE hiRSutE PATTERN
- 51. @mastermark S SCALABLE STABLE SAFE Concepts / features Self-monitoring / optimization Node strength Proactive “pull requests” Immune system Etc. Maps to… Concepts / features IDS Firewalls Perimeters Patching Virus scanning Capacity planning Performance engineering Etc. THE hiRSutE PATTERN
- 52. @mastermark E EFFICIENT ELASTIC EFFECTIVE Concepts / features Horizontal scalability Chaos Monkeys Node death Containers Microservices Growth pattern management Etc. Maps to… Concepts / features Disaster recovery Business continuity Operations System administration Etc. THE hiRSutE PATTERN
- 54. @mastermark Stigmergy “... indirect coordination between agents or actions… the trace left … by an action stimulates the ... next action...” https://goo.gl/lim73b
- 56. @mastermark
- 60. @mastermark
- 61. @mastermark