TDD for Embedded C
2021-12-03 14:10:36 UTC
Most useful learnings:
"Add test for each single line of code - before writing it" (I don't think it is practicable though)
Concepts v exercises:
Too many exercises
Presentation v discussion:
Too much discussion
James has exceptional teaching skills and is perfect in handling slides and videos. I would recommend to put a bigger emphasize of this. I would prefer to have less "hands on" (I know other colleagues see this differently).
It is not necessary after seeing the introductional video and seeing James' presentation to repeat each single step once again. I would have expected we can start from where James had put us and really learning by doing new things.
I could - if it would fit to my daily work and schedule and I see the need for.
Challenges to applying:
I am sad to say, that the legacy workshop was waste of time for me. All we made was demonstrated by James - nothing new. Fixing include issues and compiler errors by adding include directories to the makefile and adding stubs is nothing I needed to learn. The REAL thing - writing mocks for our environment - was not even touched.
"Recommend this workshop": if someone is interested in learning what TDD means: yes.
I don't consider TDD to be the only real way to develop SW.
Legacy code workshop:
Recommend to others: