Course:
TDD for Embedded C
Date entered:
2015-03-05 13:40:11 UTC
Course rating:
Very Good
Most useful learnings:
By minimizing time from coding to test you minimize time to find/fix the bugs.
Concepts v exercises:
Good balance
Presentation v discussion:
Good balance
Course improvements:
Get his network working faster.
Exercise rating:
Excellent
Exercise improvements:
More use of named enums as type definitions instead of anonymous enums or #defined values used as ints. (Seems a bit shoddy). Using enum-defined types for function parameters allows type-checking and promotes error-checking at the compiler level. Just using int values as parameters allow accidental mixing of values that might be a mix of test-code and production-code definitions.
Instructor comments:
Just would like to give a kind reminder that there are multiple ways to do things - and that 'correct-by-construction' helps code. There's a lot to be learned from the attendees. Thank you, and hope your daughter's wedding is a super wonderful time.
Better prepared:
Much better
Start tomorrow:
I can always start tomorrow. Time limitations, legacy code. Will have to carve out my own time to try to build an initial infrastructure for TDD build/test on the development system. Would try putting in one routine/file at a time (apart from the main code-base).
Challenges to applying:
Middle management wanting TDD but not realizing that it requires the very thing they have directed us not to do in the past: a system on our development machines to perform initial TDD tests off of the hardware systems.
Other comments:
The training days were worth the time.
Legacy code workshop:
No
Recommend to others:
Yes
Quote permission:
Yes