Why Put Big Ideas on Little Cards?

"... certainly it is excellent discipline for an author to feel that he must say all he has to say in the fewest possible words, or his reader is sure to skip them; and in the plainest possible words, or his reader will certainly misunderstand them..."

John Ruskin


  1. How about CRISP Builds?

    Mike Clark gave a 2004 presentation on Pragmatic Project Automation that included a description of what he called the "CRISP" criteria for build:

    Complete (recipe lists all ingredients)
    Repeatable (version control time machine)
    Informative (radiate valuable information)
    Schedulable (complete and repeatable)
    Portable (machine-independent)

    There is a similar description in the 2007 presentation “All Builds are Good”, and a more detailed description in this 2007 CT-SPIN presentation on project automation:

    • Build from scratch and independently without human intervention.

    • Must be able to create exactly the same build at a later time.
    • Store build scripts in source control.

    • "Detector of unexpected changes".
    • Provide information on why a build failed.

    • Let the builds run automatically.

    • Build should be runnable from any system (same platform), not just that of the developer.
    • For cross-platform software, it should build on all platforms.

    Is this idea flashcard-worthy?

  2. Great idea for a card, Brad--thanks for the info and links! I'd not seen this before.

  3. Done. During a meeting, I slammed it together from just the text you gave us here.

  4. I put a couple ideas for some cards together, might be a little weird. But I have found them useful on agile projects.
    Let me know if you like them or not,



Note: Only a member of this blog may post a comment.