• Course: TDD for Embedded C
  • Date entered: 2019-05-18 17:56:28 UTC
  • Course rating: Excellent
  • Most useful learnings: I already have some background in TDD, but I still learned a lot regarding details on how big steps to take in the "red-green-refactor" cycle.
  • Concepts v exercises: Good balance
  • Presentation v discussion: Good balance
  • Course improvements: Maybe a short discussion why CppUTest was used instead of, for example, Google test. If possible, it would be interesting to see a discussion or examples where TDD leads the design in the "wrong" direction. Can the design benefit from TDD?
  • Exercise rating: Very Good
  • Exercise improvements: -
  • Instructor comments: -
  • Better prepared: Moderately
  • Start tomorrow: Yes. We already use it for some areas, but I think we can add it to other areas.
  • Challenges to applying: We do not write much code by hand since we are "locked in" by tools that generate code for us.
  • Other comments: -
  • Legacy code workshop: No
  • Recommend to others: Yes
  • Quote permission: Yes