TDD for Embedded C
2021-11-12 14:52:29 UTC
Most useful learnings:
Learned, why TDD is beneficial and how it can be used to test Hardware, before Hardware becomes available. And how I should use TDD in practice.
Concepts v exercises:
Presentation v discussion:
Too much discussion
It would be useful to have short breaks during the workshop. It would also be great to have a bit more time on the technical exercises and maybe to spend less time on the end of first day discussion about likes and dislikes.
Have the homeworks and what will be done in the workshop available a bit earlier, having the time difference and being at work before the workshop made it difficult to find time to prepare.
Create a pdf only of the charts for implementation, switching between screens for sharing and looking at the town made it difficult to remember what had to be implemented. So a pdf, of the flow-chart, which could be printed out before the class could be useful.
The excercises in the first day were very easy. The second day excercises were alrigth. The third day the preparation videos got me confused, why the tests contained the read and write functions and in the implementation they were written in the flash file. For the rest, once I got the concept it was easy to implement the rest.
Excellent presenter, funny and enjoyable to follow.
Not at work, but yes.
Challenges to applying:
Currently I am not working on C or C++ projects.
The remote delivery was great. Just add some short breaks. And add printable pdf of what will be worked on the next day and not the whole course pdf.
Legacy code workshop:
Recommend to others: