Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Ex Nihilo: Why it's okay to throw away code - CodeStock 2018


Published on

Managers often have a bad reaction to hearing developers say that they need to throw away or rewrite code. Source code is expensive, taking hours/weeks/months/years of painstaking work to develop and maintain. "Why couldn't we have done it right the first time?" "Is there any way to salvage the code and reuse it somewhere else?"

This comes from a faulty view of code as the end product; in reality, the end product is the service that the code provides.

To illustrate this, take an extended construction metaphor. When constructing a house or commercial building, the blueprint is a fairly minor part of the cost. You don't want to scrimp or cut corners on the blueprint because you run the risk of far more expensive problems during the construction phase.

In software, however, the construction (build) phase is nearly free. Not only that, but a newly built "house" can be duplicated and deployed as many times as you like.

Published in: Software
  • Did you try ⇒ ⇐?. They know how to do an amazing essay, research papers or dissertations.
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Ex Nihilo: Why it's okay to throw away code - CodeStock 2018

  1. 1. Why it's okay to throw code away
  2. 2. Rob Scott m CTO @spamagnet
  3. 3. Requirements Blueprint Construction
  4. 4. 1960 μ$ 8,000,000 2015 1
  5. 5. 1960 $/month 2,430,000,000 2015 16
  6. 6. 1956 10,000,000,000 2018 40 μ$ $400
  7. 7. Nanobot design used with permission
  8. 8. MVCC (Minimum Viable Cloud City)
  9. 9. Kowloon Walled City 1989
  10. 10. Sunk cost fallacy
  11. 11. Wisdom Humans Change
  12. 12. Domain-driven Simple Loosely- coupled
  13. 13. @spamagnet Thank you!
  14. 14. other resources ● Greg Young: The Art of Destroying Software ●