Course:
TDD for Embedded C
Date entered:
2018-09-01 01:03:50 UTC
Course rating:
Very Good
Most useful learnings:
The TDD exercises for the Light Scheduler, flash driver. Learned a little more about CppUTest mocks
Concepts v exercises:
Not enough exercises
Presentation v discussion:
Too much discussion
Course improvements:
I'd rather have just gotten more practice with the concepts and exercises. This was partially our fault for not coming to day 3-4 with great material to practice on. I don't think this was wildly off the mark, just like 2-4 more hours of structured exercises over the 4 days.
Exercise rating:
Excellent
Exercise improvements:
More of them, ratio-wise.
Instructor comments:
I wasn't bothered by it much, but I thought some of the responses to questions, specifically the "Why not re-arrange these test cases and write check_for_foo_bar first" type questions, could have been a little less standoff-ish
I do think it was communicated, but he could have chosen to keep reiterating something like "for the purpose of this exercise, and to keep the class structured, I want you to work on them in this order. In reality, nobody writes test cases for you, and I think these are arranged in a manner conducive for the exercise".
Better prepared:
Much better
Start tomorrow:
I already have.
Challenges to applying:
Practice (makes perfect), applying it to the correct things, legacy code, tooling. With regards to tooling, we don't always have the type of tools in place (or even classes of tests) to make quick iteration painless.
Other comments:
Legacy code workshop:
Yes
Recommend to others:
Yes
Quote permission:
Yes