TDD for Embedded C++
2018-09-08 20:32:36 UTC
Most useful learnings:
That when doing TDD you should be sure to make the test fail before making it pass and that you should "fake it till you make it" when implementing code as a way to avoid unneeded features.
Concepts v exercises:
Too many exercises
Presentation v discussion:
Too much discussion
More formal lecture style presentations with clear topics
Make them smaller and take less time so they can be interspersed with the presentations (rather than half a day of talks followed by a half day of exercises). Also, don't do live coding in front of the group since it takes a lot of time. I felt like I spent more time watching you fix syntax errors and type than learning about TDD during the demos.
The instructor was okay, but he seemed to get a bit defensive about why he was there and why TDD was a good idea when people asked difficult questions about the advantages and disadvantages of TDD.
Challenges to applying:
Our build pipeline is still a bit too slow to really do TDD well
I think we spent too much time going over the pre-course survey content
Legacy code workshop:
Recommend to others:
Only if improved