TDD for Embedded C
2015-11-22 11:26:13 UTC
Most useful learnings:
In addition to your book I've read before: The mock usage. Seeing it used and trying by myself, it is pretty clear in minutes.
Concepts v exercises:
Presentation v discussion:
- 3 days instead of 2 ;-)
- Maybe to emphazize code smell and refactoring a bit more in the Training session: TDD is not only about generating code, but to write maintainable code. What is maintainable?
Nothing to add. They really are perfect, very well-guided small step examples and the tool chain you offer is great fun.
Not always easy to understand, but in total very impressive and helping.
Bring it on!
I've started yet. Time to expand the radius to legacy code.
Challenges to applying:
The delay of cost to benefit: The costs are effective today (learning and writing tests) and the main benefits we can earn mainly tomorrow when we see the value of good and maintainable code.
For small tasks, one might think "it's not needed", for bigger tasks "it's too complicated", when the fun of TDD isn't yet present in one's DNA.
In crisis mode, "make it work" is faster than "make it work, make it right, make it fast".
Legacy code workshop:
Recommend to others: