TDD for Embedded C++
2017-08-03 22:16:48 UTC
Most useful learnings:
Found the exploration of doubles (e.g., exploding fakes,mocks) to be of great interest and utility.
Concepts v exercises:
Presentation v discussion:
There was some confusion when we got to the legacy code section regarding installation of tools. It would be nice if the various tools and examples were fully updated to represent the latest versions of the tools.
Not sure they can be improved. They all seemed comprehensive and the cyber-dojo environment was quite easy to learn and use.
I really liked the hands-on interaction that James encouraged and supported. Most of the time it did not feel like a normal instructor vs. class dynamic but, rather, as if we were all (including James) there for the same experience and working as nothing more than engineers exploring new tools and techniques.
Bring it on!
For the most part; TDD can start tomorrow but integration of the results into the integration framework will take a bit more time as all the projects have different environments.
Challenges to applying:
Acceptance from the engineering staff although I feel comfortable that most attendees are on board. Time will tell if schedule pressures become such that people revert to what they have known for years as opposed to continuing down the proper path with what they now know. Success with TDD will have to be embraced, and continue to be embraced, at all levels of the company for this to work.
The number of hours per day was almost ideal. Not so long that people were falling off by the end of the day but long enough to cover the material.
Legacy code workshop:
Recommend to others: