• Course: Test-Driven Development
  • Date entered: 2012-02-17 14:44:01 UTC
  • Course rating: excellent
  • Most useful learnings:
  • Concepts v exercises: good balance
  • Presentation v discussion: Good balance
  • Course improvements:
  • Exercise rating: very good
  • Exercise improvements: The random scheduler thing was great; because no one figured out what it was for.
  • Instructor comments: Very positive. I liked how you were willing to criticize some students when they were clearly not paying attention.
  • Better prepared: Much better
  • Start tomorrow: Sort of. Need to figure out what to write before I figure out what to test. Typically I start out by integrating some existing code into new processor; and by the time that is done; I have a better idea about the new stuff. But that is not conducive to TDD.
  • Challenges to applying: "Coming up with tests. The reality is most code is not fully tested because the degenerate conditions don't happen (we call it properly). Using TDD makes harder to draw the line between ""wasteful testing"" and ""useful testing""."
  • Other comments: You directly emailed everyone that you would send out a pre-course exercise; but never did. I had to get it from random XXXX person. Not about James; but the internal communications leading up this course were AWFUL. Multiple people were sending emails about it; but no one responded to inquiries.
  • Legacy code workshop: Yes
  • Recommend to others: yes
  • Quote permission: no