Clean Code - objectmentor.com

• Ward Cunningham's Observation
  • bullets
    • "it was too easy to make a mess in Smalltalk."
    • Have you ever been significantly impeded by bad code?
      • Why did you write it?
• Notes
  • Wrath of Khan - lol
  • Rough Draft
    • Second Draft
      • Third draft
  • always test - autotest?
• What do we do about bad code?
  • bullets
    • The Grand Redesign in the sky?
    • Incremental Improvement
  • notes
    • requirements / redesign / tiger team
    • face the mess that you made, and clean it up
  • Incremental Improvement
    • Always check code in better than you checked it out
    • Never let the sun set on bad code.
    • Test First!
      • Provides the necessary flexibility
• Clean Code: Args
  • bullets
    • An exploration of amess that got cleaned
    • It's a command line argument tool
• Symmetry here
  • Bunch of if statements
  • Lots of duplication
  • original design pattern did not scale
  • DRY - modify one location
    • 0 if possible
  • notes
    • too many variables
    • three hash sets, and the if/else chains
    • stll have to add number lists to it
    • all leads up to a:
      • FESTERING PILE
        • didn't start out that way
          • it started out clean
          • the mess built up over time
          • initial structure didn't scale up well
          • the more it grew the worst it got
          • eventually i had to stop
• On Incrementalism
  • One of the best ways to ruin a program
    • Make massive changes in the name of improvement
    • it's hard to get the program working again
  • TDD: Keep the system running at all times!
    • I am not allowed to make a change that breaks the system
    • Every tine change I make must keep the system working
• So I started to Refactor
  • always testing
  • make tiny steps
    • check for pass / fail
• Bad Code
  • Nothing more degrading than bad code
  • Bad schedules can be redone
  • Bad requirements can be redefined
  • Bad team dynamics can be resolved - Fire the asshole (lol)
  • Bad code rots and ferments
  • It becomes an inexorable weight that drags the team down
• Professioanl Behavior
  • The "green Band" - testing reminder
  • Professionals write tests -- first
  • professionals clean their code
  • Professionals know that the only way to go fast
    • is to go well
• DHH Observation
  • "It's about making things a little bit nicer"
    • The check in rule