• Course: Test-Driven Development
  • Date entered: 2012-02-03 02:31:59 UTC
  • Course rating: excellent
  • Most useful learnings: Several techniques applicable to deal with legacy codes; to make them testable first before refactoring.
  • Concepts v exercises: good balance
  • Presentation v discussion: Good balance
  • Course improvements: "For SLB; which deals with ""measurements""; examples of ""measuring something"" (interfacing fake A/D converter; saving data into mock Flash memory; etc.) would be very interesting. "
  • Exercise rating: excellent
  • Exercise improvements: I think it was good to focus on C; not C++ this time; when I look at skillset of the other participants. I personally would like to do more exercise in C++ (well; homework I can do alone; for sure).
  • Instructor comments: This time; more than a half of participants were non Japanese. I'm afraid some Japanese students had hard time to catch up talks in English; sometimes.
  • Better prepared: Bring it on!
  • Start tomorrow: Yes; I will. I have a plan to write a small code for architecture prototype; and will try to make it by TDD-ing.
  • Challenges to applying: Major challenge will be to bring people in a team to reasonablly at same technical level; keep consistent mindset. Doing it alone is easy; but will not pay off as much as done by team.
  • Other comments: I will read James's book one more time again; and may come back with comments/suggestions (if at all possible). Some stories from Motorola etc. were very interesting; and highly appreciated.
  • Legacy code workshop: Yes
  • Recommend to others: yes
  • Quote permission: yes