Code Kata / Pragmatic Programmer guy

http://codekata.pragprog.com/2007/01/kata_seven_howd.html

Now we need to do some acting. Read through this code three times. Each time through, pretend something different. Each time, jot down notes on the stuff you find.

    * The first time through, pretend that the person who wrote this code is the best programmer you know. Look for all the examples of great code in the program.
    * The second time through, pretend that the person who wrote this code is the worst programmer you know. Look for all the examples of horrible code and bad design.
    * The third (and last) time though, pretend that you’ve been told that this code contains serious bugs, and that the client is going to sue you to bankruptcy unless you fix them. Look for every potential bug in the code.

Now look at the notes you made. What is the nature of the good stuff you found? Would you find similar good stuff in the code you’re writing today. What about the bad stuff; are similar pieces of code sneaking in to your current code too. And finally, did you find any bugs in the old code? If so, are any of them things that that you’d want to fix now that you’ve found them. Are any of them systematic errors that you might still be making today?

I have a morning ritual that I need to share. I call it 'the sussman'. First I crouch down in the shower in the classic 'I put on my robe and wizard hat' pose. With my eyes closed I crouch there for a minute, visualizing either Sussman or Abelson and I start to hum the SICP theme. Then I slowly rise to a standing position and open my eyes. It helps me to proceed through my day as an emotionless EXPERT PROGRAMMER. The only problem is if the shower curtain sticks to my sussman leg. It ruins the fantasy.