No Code is Better Than No-Code

The more code I write, the more I believe that: We should think of code as liabilities instead of assets. So removing code is better than adding code. And eventually, no code is better than no-code.

  1. Write code that is easy to delete, not easy to extend — programming is terrible

    • Every line of code written comes at a price: maintenance.

      My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent"

    • Good code isn't about getting it right the first time.

      Good code is just legacy code that doesn't get in the way.

  2. Michael Feathers: The Carrying-Cost of Code: Taking Lean Seriously

    • The future belongs to organizations that learn how to strategically delete code.
    • Carrying costs are larger than we think.
  3. 94: Ben Orenstein - The Art of Pairing - Full Stack Radio

    Think of code as both assets and liabilities

  4. Chad Fowler on Twitter: "Instead of optimizing for code that can live a long, healthy life, optimize for constantly destroying and replacing code inside systems that live a long healthy life. Code should be impermanent by design. Code is fuel.…"
  5. ☕ J. B. Rainsberger on Twitter: "Writing code to throw it away ironically increases the need to design well, rather than decreasing it."
  6. Adding more code is a code smell - dsdshome