mend things
play

mend things @KevlinHenney Move fast and break things - PowerPoint PPT Presentation

Move slow and mend things @KevlinHenney Move fast and break things https://twitter.com/KevlinHenney/status/922803893167427584 speed velocity v = v x + v y v = | v | v = s _ t s t s t s [T] [T] t utilisation estimation accuracy


  1. Move slow and mend things @KevlinHenney

  2. Move fast and break things

  3. https://twitter.com/KevlinHenney/status/922803893167427584

  4. speed

  5. velocity

  6. v = v x + v y

  7. v = | v |

  8. v = s _ t

  9. s t

  10. s t

  11. s [T] [T] t

  12. utilisation

  13. estimation accuracy

  14. Orient Observe Understand where Gather information from a range of you're at and where sources you want to be Act Decide Carry out the plan Develop a plan for action Boyd's OODA Loop

  15. Act Decide Carry out the plan Develop a plan for action Orient Observe Understand where Gather information you're at and where from a range of sources you want to be Boyd's OODA Loop

  16. Do Plan Carry out plan Establish hypothesis, goal or work tasks Act Study Revise approach Review what has or artefacts based been done against plan (a.k.a. Check ) on study Deming/Shewhart Cycle

  17. You have to finish things — that's what you learn from, you learn by finishing things. Neil Gaiman

  18. code tests scripts

  19. codified knowledge

  20. knowledge acquisition

  21. learning

  22. communication

  23. social negotiation

  24. model of participation

  25. The biggest advantage of autonomously working teams is risk reduction through increased group intelligence. Kevlin Henney https://jaxlondon.com/blog/java-core-languages/the-error-of-our-ways-kevlin-henney/

  26. There’s little correlation between a group’s collective intelligence and the IQs of its individual members. But if a group includes more women, its collective intelligence rises. "What Makes a Team Smarter? More Women" Anita Woolley & Thomas W Malone http://hbr.org/2011/06/defend-your-research-what-makes-a-team-smarter-more-women/

  27. The four conditions that characterize wise crowds: diversity of opinion, independence, decentralization, and aggregation.

  28. Aligning a poorly performing IT organization to the right business objectives still won’t get the objectives accomplished. Richard F Connell David Schpilberg, Steve Berez, Rudy Puryear and Sachin Shah "Avoiding the Alignment Trap in Information Technology " MIT Sloan Management Review http://sloanreview.mit.edu/article/avoiding-the-alignment-trap-in-it/

  29. The first rule of scaling agile is… don't do it! Or rather, try to avoid it for as long as you possibly can. Andreas Rowell First Rule of Scaling Agile – DON'T! https://www.linkedin.com/pulse/first-rule-scaling-agile-dont-andreas-rowell/

  30. Software development does not have economies of scale. Development has diseconomies of scale. Allan Kelly Beyond Projects http://www.slideshare.net/allankellynet/no-prokects-beyond-projects-refreshed-version

  31. 𝑢 = 𝑢 1 completion time for one person

  32. 𝑢 = 𝑢 1 𝑜 division of labour

  33. 𝑜 − 1 Amdahl's law 𝑢 = 𝑢 1 1 − 𝑞 𝑜 portion in parallel

  34. 𝑜 − 1 + 𝑙 𝑜 𝑜 − 1 𝑢 = 𝑢 1 1 − 𝑞 𝑜 2 connections (worst case) communication overhead (typical)

  35. 𝑜 − 1 + 𝑙 𝑜 𝑜 − 1 𝑢 = 𝑢 1 1 − 𝑞 𝑜 2

  36. The Facebook iOS app has over 18,000 Objective-C classes, and in a single week 429 people contributing to it. Facebook's code quality problem Graham King http://www.darkcoding.net/software/facebooks-code-quality-problem/

  37. Architecture is a hypothesis, that needs to be proven by implementation and measurement. Tom Gilb

  38. “Move fast and break things” [...] — Is this a good or a bad thing? JAX London https://jaxlondon.com/blog/java-core-languages/the-error-of-our-ways-kevlin-henney/

  39. It is a context-specific thing. When applied within the appropriate context it can be considered a good thing, an invitation to experiment freely and without restraint, to discover new ways of working and thinking, to break out of an overly comfortable or stuck place. Kevlin Henney https://jaxlondon.com/blog/java-core-languages/the-error-of-our-ways-kevlin-henney/

  40. On the other hand, when applied outside the appropriate context it can undermine people and their work, can come across as irresponsible, arrogant and lacking in self- awareness. I would consider this a bad thing. Kevlin Henney https://jaxlondon.com/blog/java-core-languages/the-error-of-our-ways-kevlin-henney/

  41. https://twitter.com/tackline/status/757562488363843584

  42. Knight Capital Group realized a $460 million loss in 45 minutes. Doug Seven https://dougseven.com/2014/04/17/knightmare-a-devops-cautionary-tale/

  43. The update to SMARS was intended to replace old, unused code referred to as “Power Peg” — functionality that Knight hadn’t used in 8 -years. Doug Seven https://dougseven.com/2014/04/17/knightmare-a-devops-cautionary-tale/

  44. The code that that was updated repurposed an old flag that was used to activate the Power Peg functionality. Doug Seven https://dougseven.com/2014/04/17/knightmare-a-devops-cautionary-tale/

  45. Why code that had been dead for 8 years was still present in the code base is a mystery, but that’s not the point. Doug Seven https://dougseven.com/2014/04/17/knightmare-a-devops-cautionary-tale/

  46. Dev

  47. During the deployment of the new code, however, one of Knight’s technicians did not copy the new code to one of the eight SMARS computer servers. Securities and Exchange Commission https://www.sec.gov/litigation/admin/2013/34-70694.pdf

  48. Knight did not have a second technician review this deployment and no one at Knight realized that the Power Peg code had not been removed from the eighth server. Securities and Exchange Commission https://www.sec.gov/litigation/admin/2013/34-70694.pdf

  49. Ops

  50. Dev Ops

  51. The failure resulted in a loss of more than US$370 million. http://en.wikipedia.org/wiki/Cluster_(spacecraft)

  52. v = v x + v y

  53. v = | v |

  54. Simple Testing Can Prevent Most Critical Failures An Analysis of Production Failures in Distributed Data-Intensive Systems https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-yuan.pdf

  55. Almost all catastrophic failures are the result of incorrect handling of non-fatal errors explicitly signalled in software. https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-yuan.pdf

  56. A majority of the production failures (77%) can be reproduced by a unit test. https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-yuan.pdf

  57. Testing Is the Engineering Rigor of Software Development Neal Ford

  58. Do Plan Carry out plan Establish hypothesis, goal or work tasks Act Study Revise approach Review what has or artefacts based been done against plan (a.k.a. Check ) on study Deming/Shewhart Cycle

  59. Reify Write Implement so that Create or extend a test case for new the test passes behaviour — as it's new, the test fails Refactor Reflect Make it so! Is there something in the code or tests that could be improved? Test-First Cycle

  60. Development needs to go further than the technical stack; the full stack includes the world and people around the software. Kevlin Henney https://jaxlondon.com/blog/java-core-languages/the-error-of-our-ways-kevlin-henney/

  61. http://www.michaeleisen.org/blog/?p=358

  62. http://www.michaeleisen.org/blog/?p=358

  63. http://www.michaeleisen.org/blog/?p=358

  64. http://www.bbc.co.uk/news/business-37582150

  65. S-Programs P-Programs E-Programs Meir M Lehman "Programs, Life Cycles, and Laws of Software Evolution"

  66. S-Programs Programs whose function is formally defined by and derivable from a specification. Meir M Lehman "Programs, Life Cycles, and Laws of Software Evolution"

  67. P-Programs Despite the fact that the problem to be solved can be precisely defined, the acceptability of a solution is determined by the environment in which it is embedded. Meir M Lehman "Programs, Life Cycles, and Laws of Software Evolution"

  68. E-Programs Programs that mechanize a human or societal activity. The program has become a part of the world it models, it is embedded in it. Meir M Lehman "Programs, Life Cycles, and Laws of Software Evolution"

  69. Always design a thing by considering it in its next larger context. Eliel Saarinen

  70. We show, via a massive (N = 689,003) experiment on Facebook, that emotional states can be transferred to others via emotional contagion, leading people to experience the same emotions without their awareness. http://www.pnas.org/content/111/24/8788.full

  71. A/B testing

  72. As mankind relies more and more on the software that controls the computers that in turn guide society, it becomes crucial that people control absolutely the programs and the processes by which they are produced, throughout the useful life of the program. Meir M Lehman "Programs, Life Cycles, and Laws of Software Evolution"

  73. Move fast and break things

  74. Move slow and mend things

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend