TDD for Embedded C
2017-09-21 07:46:01 UTC
Most useful learnings:
Keep the feedback loop short, do many small iterations instead of several big ones. Also using a more object-oriented design strategy for C programs (splitting up interfaces in header files) was not entirely new, but I had not seen it used this way before and I really liked that.
Using these design-tools specifically to add testing points was nice.
Concepts v exercises:
Presentation v discussion:
The flow of the presentation slides
Turn on syntax highlighting in Code Dojo by default
I really liked the loose approach, with the 'parking lot' for questions that couldn't be answered just yet. Also liked the excercises a lot, and the balance between us watching you do the programming, us doing the programming and you analysing our mistakes was very good.
Bring it on!
Yes. We already use pretty extensive testing, but I feel like I have a better grasp on designing specifically for testing now.
Challenges to applying:
We work on algorithmic problems, where it's often hard to separate the algorithm in small enough chunks to test them in a practical way.
Legacy code workshop:
Recommend to others: