16 Comments on “Three Flaws in Software Design – Part 4: Incremental Development & Design + Wrap-up”

  1. *3 Flaws In Software Design: Part 4: Incremental Development & Design*
    #design #developers #software

    In the final installment of this week’s series, +Jeremy Walker & +Max
    Kanat-Alexander discuss a development process that allows one to avoid the
    Three Flaws of Software Design from Max’s book Code Simplicity: The
    Fundamentals of Software.

    Link to presentation: http://goo.gl/h73nY3

  2. I discuss Incremental Development and Design with +Google Developers.

  3. Finally someone saying this!
    I always assumed the first step of every sprint should be design and
    re-factoring – then I learned that no one was doing this!

  4. The trade-off here is obvioulsy design/testing. Revolutions in virtually
    every step in the development causes to rebuild whole test suites. If you
    design the system accounting possible future changes, the risk is to waste
    a lot of time or to have a little idea of what you’ll really need later in
    the process. I think the key is always find the right equilibria

  5. If you believe in iterative development, you should also be doing iterative
    design
    Three Flaws in Software Design – Part 4: Incremental Development & Design +
    Wrap-up

  6. Three Flaws in Software Design – Part 4: Incremental Development & Design +
    Wrap-up

  7. The overall series was a really helpful reminder on how to avoid shooting
    yourself in the foot when writing software.

    Personally, I found this part the most useful one.

Comments are closed.