TDD for Embedded C++
2018-09-01 04:53:03 UTC
Most useful learnings:
To take small steps and to choose much more meaningful names to tests and test phases.
Concepts v exercises:
Presentation v discussion:
I tended to zone out a bit in the last 2 days. Perhaps an exercise or 2 that use TDD principals in a non-software environment?
I enjoyed the pair and small team collaboration, but found the mobbing too unwieldy, and the noise level often hit the point where I couldn't hear anyone because all I could hear were voices.
Engaging, personable. Very knowledgeable, with the "war stories" to back up assertions. Good examples drawn from experience.
Challenges to applying:
As requirements, design, tests, etc. go through the Development Assurance Level (DAL) reviews, things get locked down. What I want to do is take a couple of months to go over my code in a paired programming mode, revamp and refactor as I go to make it much better and THEN tackle the DAL reviews. Applying TDD techniques to code that is rapidly being encapsulated in amber will be challenging.
It was a worthwhile experience that gave me insight into how I write/test code and how I can uplift myself.
Legacy code workshop:
Recommend to others: