Course:
TDD for Embedded C
Date entered:
2015-11-02 14:00:36 UTC
Course rating:
Very Good
Most useful learnings:
Unit testing is requirement thorough the development cycle
Concepts v exercises:
Good balance
Presentation v discussion:
Too much discussion
Course improvements:
1st day the content was very light. The discussion on the 'survey' and the 'sticky notes' provided me very little value. Without those the material was about 4 hrs for a full day of training.
I expected 8 hrs of training (8:30-5:00 with 30 minute lunch)
Exercise rating:
Very Good
Exercise improvements:
More complexity. Not a standalone module but something from a more complex legacy embedded system.
Instructor comments:
Kept me engaged.
Consider how to bend the rigidity of TDD to fit customer needs.
TDD is a method. Can it be decoupled from CppUTest.
Better prepared:
Much better
Start tomorrow:
No. I/we don't introduce many 'new' modules so this needs to be applied to legacy code, and the investment in TDD on legacy code is too much.
Challenges to applying:
investment in TDD on legacy code is too much
Other comments:
Legacy code workshop:
No
Recommend to others:
Yes
Quote permission:
Yes