TDD for Embedded C
2021-11-08 12:31:13 UTC
Most useful learnings:
That i write bugs, ehm sorry, tests :-)
Iterate you code with smalls steps and therefore set a focus.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
Too much presentation
Maybe do more and shorter excercises. Split the excercises in smaller portions and discuss them shortly. Then go on with the next part of the excercise.
The last part of each day was a bit hard to listen to you and watch you do coding for such a long time. Alternating: Theory and examples.
More focus on the TDD methodology and a bit less code engineering. We spent a lot of time during the excercises finding the right solution. Dont get me wrong, for a C developer the excercises were not difficult!
Maybe think of providing more prepared samples or guidances. Maybe it was also a problem of not being aware of all your hints...
We as a team think we would be ready. We have to challenge our toolchain (build times) and our SW process.
But we think we could start soon. We have to provide unit test anyway (medical).
Challenges to applying:
Legacy code workshop:
Recommend to others: