TDD for Embedded C++
2019-08-22 22:35:06 UTC
Most useful learnings:
How to improve the code review process.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
Too much presentation
Instead of making the first day a presentation proclaiming TDD's virtues, jump right in with an experience demonstrating them.
Perhaps as an initial exercise, have people implement (until working) a thing without any test automation. Perhaps have them rely on an external library with no implementation details available and whose documentation is slightly incorrect.
When time is up or when they're done, have them implement the same thing but against a different, also wrong implementation of that resource, but this time use TDD, so they can find the inconsistency early.
In general, the instructor provided value and pedagogy. However, our first day felt less productive than I expected and it's my perception that this was no fault of the students. I felt the instructor had a defensive posture but I couldn't figure out why.
Bring it on!
Challenges to applying:
Not a big challenge, but there are a handful of people who claim to have had bad experiences with TDD and those same people are now managers. So some people might have an uphill battle getting the allowance to experiment with it.
Legacy code workshop:
Recommend to others:
Only if improved