• Course: TDD for Embedded C
  • Date entered: 2020-04-16 19:10:48 UTC
  • Course rating: Excellent
  • Most useful learnings: The TDD development process (in combination with learning surface level of tools like CppUTest/fff/etc)
  • Concepts v exercises: Good balance
  • Presentation v discussion: Good balance
  • Course improvements: I think the wealth of resources presented on your website will help support a change in software development habits going forward. The concepts of TDD were clearly explained. Some of the exercises had some ambiguity to the path forward which I found distracting to the goal of learning/practicing TDD on simple coding exercises, however many probably did not feel this and perhaps some of it was introduced in user error! Seems to provide a great jumping off point to change development practices to TDD (though courses teaching habits are hard to evaluate directly after without time to implement these habit changes). An exercise on the last day would have been nice, but lots of material was covered.
  • Exercise rating: Very Good
  • Exercise improvements: Possibly remove subtlety from instructions. The risk reward of someone missing it and floundering for a bit vs understanding and making more lasting connections through discovery :)
  • Instructor comments: Very knowledgeable of subject matter. Open to questions/discussion at all times. Fun sense of humor. Kept class moving well.
  • Better prepared: Bring it on!
  • Start tomorrow: Yes, personal project to scratch my programming itch (lots of hardware development currently at work). Will begin planning new project software using TDD principles (mock drivers, software dev before boards back, etc) when time permits.
  • Challenges to applying: Finding and getting comfortable with a C Unit Test harness. Setting up Jenkins for simulated environment, board environment, adjusting coding habits. All of these are on me, I do not have resistance from colleagues/management.
  • Other comments: Half days worked very well. Allows learning without grinding work to a halt! Thanks for being flexible with that (know the original schedule was different, not sure how it was different).
  • Legacy code workshop: No
  • Recommend to others: Yes
  • Quote permission: Yes