• Course: TDD for Embedded C++
  • Date entered: 2018-11-29 21:01:03 UTC
  • Course rating: Good
  • Most useful learnings: Increased use of interfaces will be very helpful, even if they are just to split untested classes into a true implementation and a spy. This should allow tests to be introduced to legacy code with lower risk. Honorable mention: Using test doubles to emulate hardware/the OS.
  • Concepts v exercises: Good balance
  • Presentation v discussion: Good balance
  • Course improvements: While the balance of presentation/discussion and exercises was good, I would have preferred that the exercises be smaller and more frequent (as opposed to a single 2.5 hour block). Concrete examples of adding tests to legacy code would also have been helpful.
  • Exercise rating: Good
  • Exercise improvements: The exercises from day 1 and 2 could be shortened a bit. The point of each exercise was made clear long before the 2.5 hour window ran out.
  • Instructor comments:
  • Better prepared: Much better
  • Start tomorrow: No. I first need to spend some time convincing other developers that adding tests to our legacy code is worth the risk and effort if done correctly.
  • Challenges to applying: There is strong reticence on our to refactor legacy code, especially among the senior developers.
  • Other comments:
  • Legacy code workshop: Yes
  • Recommend to others: Yes
  • Quote permission: No