Course:
TDD for Embedded C++
Date entered:
2014-08-08 23:02:13 UTC
Course rating:
Good
Most useful learnings:
The nuts and bolts of using cpputest, and the basic TDD methodology/philosphy. If I get nothing else out of the course, I at least will know what "TDD" means.
Least useful: Design patterns. Too abstract - what USE are they?
Concepts v exercises:
Good balance
Presentation v discussion:
Good balance
Course improvements:
Tone down the level of abstraction in presentation and exercise examples. Don't use sub-sub-sub-...-classes to demonstrate something where a simple single class will do.
Try to stress the practical more.
Exercise rating:
Good
Exercise improvements:
Early sample problems should provide more hand-holding, perhaps even down to the "enter this now" level (or close to it) to help people get more used to the syntax before they actually have to think about application.
Instructor comments:
James has a (mostly) down-to-earth presentation style that I appreciated. His willingness to interrupt his presentation to answer questions or explain things in more detail was appreciated.
Better prepared:
A little
Start tomorrow:
I can try these techniques on code that I write as part of my learning C++ exercises (this is a self-study I am presently working on).
I do not see how I can use TDD techniques on legacy code. Too complex/difficult.
Challenges to applying:
Some unit testing is used in our present codebase, but not everyone is up to speed on TDD, and there may be some resistance to adoption. Will I be given the freedom and granted the time to learn and adopt TDD methods?
Other comments:
This course may not have been appropriate for me because I am not an experienced _C++_ programmer. C++-specific concepts were foreign to me and I spent more time puzzling out C++ syntax then I did working with the TDD nuts & bolts.
Legacy code workshop:
No
Recommend to others:
Yes
Quote permission:
Yes