• Course: Test-Driven Development
  • Date entered: 2012-03-09 07:50:53 UTC
  • Course rating: good
  • Most useful learnings: The different techniques for breaking dependencies and how these methods will improve the code design.
  • Concepts v exercises: good balance
  • Presentation v discussion: Good balance
  • Course improvements: There was a lot of overlap between the book and the course. 99% don't read the book before the course but for the ones who do they get the information twice. An even fewer number might have actually tried the techniques. The information is good and the repetition as well so I don't know how it can really be improved. Maybe a cheat sheet could be developed listing the different techniques for breaking dependencies/finding seams and references to where to find them together with pros and cons. Or a small example for each. Could be a nicely styled PDF for printing on a poster.
  • Exercise rating: very good
  • Exercise improvements: Nice to have some traps in them that reflects the real world later on. Good to talk about pair programming and show the benefits.
  • Instructor comments: The instructor has a lot of experience with embedded and the examples really targets the often overlooked niche of ESW. He is pedagogic and has a good pace making sure that everyone is on the same page.
  • Better prepared: Much better
  • Start tomorrow: I think I have all the necessary tools to start breaking dependencies in my legacy code and testing code that I from now on touch.
  • Challenges to applying: Huge functions with multiple dependencies make some of them very hard to test. Even a small change would trigger the boy scout rule and the implications for testing a small change in one of those function would be huge.
  • Other comments: Thanks James; I really enjoyed the course!
  • Legacy code workshop: Yes
  • Recommend to others: yes
  • Quote permission: yes