TDD for Embedded C
2019-02-27 19:20:40 UTC
Most useful learnings:
Details about the CppUTest framework and TDD itself.
Concepts v exercises:
Presentation v discussion:
Clear, methodical, informative.
No. Not actively working on a client project at this time.
Challenges to applying:
Though individuals should advocate for better ways of working, developers often disagree about the best way(s) to work. Also, managers are the ultimate arbiter of methodology, since they pay directly for development tools and indirectly for productivity. For example,it's not very feasible to have some developers using C# while others use LISP; some using TDD, but not others. I've had developers scold me for removing "their" dead code. Someone who doesn't understand basic quality concepts isn't likely to understand more advanced concepts.
It's very difficult to make remote delivery as interactive as live instruction. The remote delivery for this class was probably about as good as it gets.
Legacy code workshop:
Recommend to others: