Course:
TDD for Embedded C
Date entered:
2015-04-16 21:56:37 UTC
Course rating:
Fair
Most useful learnings:
Using mock to create response stimulus allows easy testing of the error paths. Not always easy to do. Also like the methodology in general - avoid code bloat trying to second guess requirements and you end up with tested code.
Concepts v exercises:
Too many exercises
Presentation v discussion:
Too much discussion
Course improvements:
It was longer than it needed to be for experience programmers.
Exercise rating:
Good
Exercise improvements:
Fewer programming steps. The interesting piece was when the requirements change and you see how quickly you can accommodate that change by running the tests.
Instructor comments:
focus on the methodology rather than implementation choices and programming style.
Better prepared:
Much better
Start tomorrow:
Yes. I can see applying this immediately.
Challenges to applying:
poor simulation environment.
Other comments:
Legacy code workshop:
Yes
Recommend to others:
Only if improved
Quote permission:
Yes