TDD for Embedded C++
2018-02-01 00:18:04 UTC
Most useful learnings:
CppUTest is a good, simplified alternative to google test that is easy to use for embedded projects, and I'll definitely leverage it. Learned that I really don't like mob programming, but it was great to try it and find that out.
Concepts v exercises:
Presentation v discussion:
Tie in or refer to the book a little more in a discussion, at least to make it clear that answers for things that we may have glossed over are probably available there.
Pairing was awkward sharing cyberdojo between two computers and users. Since this probably can't work better without a different system, it might make more sense to recommend individuals work alone and encourage collaboration between them (in which case the system would work very well).
James is a fantastic teacher. He is an expert in the field and an evangelist for his technique without being overbearing about it. Very pragmatic approach.
Yes, I definitely have a lot more confidence in the approach having seen it work.
Challenges to applying:
Refactoring for legacy code can be very hard. We were taught that this is no excuse, but in practice on the third day we really did reinforce this fear. The benefits are understood, but justifying so many changes required to make code testable to fix a small bug will be a hard mental roadblock that will have to be crossed.
Legacy code workshop:
Recommend to others: