• Course: TDD for Embedded C
  • Date entered: 2017-05-08 08:33:07 UTC
  • Course rating: Very Good
  • Most useful learnings: That my TDD practicing up until now has not been optimal: I did follow the Write test, Make it fail, Make it pass pattern, but I would apply this pattern in developing all expected features of a class a long time before they were were actually *needed* by the rest of the system. I.e. develop the entire class, including features I would not need until after (say) two more days of development work. (Premature development of APIs, e.g.) The risk in my old approach is to develop e.g. an API I may need to re-architect two days later. After this class, I will change this habit, and develop only what is needed right now by the code.
  • Concepts v exercises: Good balance
  • Presentation v discussion: Good balance
  • Course improvements:
  • Exercise rating: Excellent
  • Exercise improvements:
  • Instructor comments: I liked the fact that you bring up real-life examples from your own experience.
  • Better prepared: Bring it on!
  • Start tomorrow: Yes.
  • Challenges to applying: None really, as TDD is already an accepted practice where I work :-)
  • Other comments:
  • Legacy code workshop: No
  • Recommend to others: Yes
  • Quote permission: Yes