how did we end up here
play

How did we end up here? Todd Montgomery - @toddlmontgomery Martin - PowerPoint PPT Presentation

Jul 19, 2023 •662 likes •1.84k views

How did we end up here? Todd Montgomery - @toddlmontgomery Martin Thompson - @mjpt777 How bad can things really be? Software Project Success Rates Successful Challenged Failure Ad-hoc 49% 37% 14% Iterative 61% 28% 11% Agile 60% 28%

  1. How did we end up here? Todd Montgomery - @toddlmontgomery Martin Thompson - @mjpt777

  6. How bad can things really be?

  7. Software Project Success Rates Successful Challenged Failure Ad-hoc 49% 37% 14% Iterative 61% 28% 11% Agile 60% 28% 12% Traditional 47% 36% 17% - Dr Dobbs 2010

  8. Software Project Success Rates – by Team Size < 10 11 - 25 > 25 Ad-hoc 70% 58% 40% Iterative 88% 68% 55% Agile 83% 70% 55% Traditional 69% 51% 50% - Dr Dobbs 2010

  9. Well that’s the optimistic view!

  10. Software Project Success Rates Successful: 32% Challenged: 44% Failure: 24% – Standish Group Chaos Report 2010

  11. Software Project Failure Rates < $350,000: 20% $350,000 - $1,000,000: 25% > $1,000,000: 28% – Gartner 2012

  12. “...the larger the company, the greater the chance that what drives tech investments isn't what's best for the business, but what's best for the decision- maker's career.” – Information Week (EA Section)

  13. Sacred Cows - It’s BBQ Time!!!

  14. Enterprise Software

  15. ent • ter • prise noun \ ˈ en-t ə (r)- ˌ prīz \ : a project or activity that involves many people and that is often difficult : the ability or desire to do dangerous or difficult things or to solve problems in new ways Source: http://www.merriam-webster.com/

  17. Enterprise Software Are you selling code, people, or one-throat-to-choke?

  19. Product Management

  20. Minimum Viable Product ?

  21. Product Owner ?

  23. Technologists ARE part of the business

  24. Take responsibility for ROI

  25. Agile Methods

  28. Water-scrum-fall

  29. What really matters?

  30. Need to focus on learning, feedback cycles, and outcomes

  31. There is an uncomfortable truth…

  32. Bug Triage

  33. tri • age noun \ trē - ˈ äzh, ˈ trē - ˌ \ : the sorting of and allocation of treatment to patients and especially battle and disaster victims according to a system of priorities designed to maximize the number of survivors. Source: http://www.merriam-webster.com/

  35. “Worse is Better...”

  36. Really???

  38. “The bitterness of poor quality is remembered long after the sweetness of a low price is faded from memory.” - Aldo Gucci 1938

  40. Shared Mutable State

  41. Shared Mutable State... the most feared words in computing

  42. …if not they should be!

  45. Shared Mutable State should only be used for systems programming

  46. Embrace append-only, single writer, and shared nothing designs

  47. If you don’t... math will hunt you down and there is nowhere to hide!

  48. Universal Scalability Law 20 18 16 14 12 Speedup 10 8 6 4 2 0 1 2 4 8 16 32 64 128 256 512 1024 Processors Amdahl USL

  49. Text Encoding

  51. But it’s human readable...

  52. Binary is hard to work with...

  55. Big Data

  56. Communications Battery life and bandwidth?

  57. Synchronous Comms

  58. Bad things will happen!!!

  59. Synchronous Communication is the crystal meth of distributed programming

  60. Causes a coupling in location and time

  61. Errors need to be first class messages

  62. Full-duplex vs Half-duplex

  63. Are your micro services on crystal meth?

  64. Abstraction

  65. “All non -trivial abstractions, to some extent, are leaky.” - Joel Spolsky

  66. “The detail of underlying complexity cannot be ignored.”

  67. “the purpose of abstracting is not to be vague, but to create a new semantic level in which one can be absolutely precise” - Dijkstra

  68. We could say the main issue is that people don’t understand abstractions...but...

  69. Sins committed in the name of Abstraction

  70. ORMs !!!

  71. Functional Programming

  72. What is the biggest issue with functional programming?

  73. Functional Programmers

  74. Functional programming is NOT the answer to multi-core

  75. Software Transactional Memory was a failed experiment!

  76. No Mechanical Sympathy?

  77. “...software is not constrained by the physical world... d on’t be a douche” - FP Fanboi

  80. However there is genuine brilliance in functional programming

  81. Collaborate and great things can happen...

  82. Cloud Computing

  83. Why has cloud computing taken off?

  84. BOFH

  85. Business Prevention Office

  86. Opportunity Cost!!!

  87. “Optimise for speed of delivery and you will deliver so fast you reduce costs” - Adrian Cockcroft

  88. Virtualization

  91. Jigsaw

  92. Throw hardware at it… development is too expensive

  93. The free lunch is over…we cannot be sloppy anymore…

  94. Loops L0 1534 µops LB 28 µops LB 28 µops

  95. Code must be simple and composable

  96. Cache Sub-System MOB L0(I) – 1.5k µops 128 bits / cycle 16 Bytes / cycle TLB LF/WC Pre-fetchers Buffers L1(D) - 32K L1(I) – 32K 32 Bytes / cycle 32 Bytes / cycle TLB Pre-fetchers L2 - 256K 32 Bytes / cycle Ring Bus QPI Bus QPI PCI-e Memory Controller Controller Memory L3 – 8-20MB System Agent Channels

  97. Patterns of access and locality are key to performance

  98. Memory Sub-System Performance Accumulated Bandwidth Improvement Latency Time

  99. What does this mean for software?

  100. Diversity

Recommend

More recommend