TDD for Embedded C++
2018-02-02 15:56:38 UTC
Most useful learnings:
How to separate classes properly and only include methods within a class that contribute to the primary functionality of that class. This makes testing a lot simpler.
Concepts v exercises:
Presentation v discussion:
Too much presentation
I think James should be a little more involved with the teams during the paired programming exercises. I also think that for the legacy code section, the team should be given notice far in advance so that they can choose a good project/files/classes that they want to practice TDD on.
I would recommend doing some more mobbing so that James can be explaining anything that is confusing to anyone at any given time. Sometimes pairs would get stuck and might hesitate to ask for help or James would be busy with another pair. Mobbing would alleviate this.
James is very thorough and detailed with his explanations of TDD concepts.
Probably not because my focus is more on the Android side so I would need some experience with that first.
Challenges to applying:
Since I deal with UI and rely on Bluetooth and Wifi, it is challenging for me to apply these ideas.
Legacy code workshop:
Recommend to others: