TDD for Embedded C
2020-03-26 20:05:23 UTC
Most useful learnings:
It is easier to keep the code working than fixing it after you break it. I often make my modification in batch mode and then have to fix all the compiler errors for the next hour(s). So seems sensible to reduce the pace to gain in overall speed.
Concepts v exercises:
Presentation v discussion:
The chat questions could be handled a bit quicker. But I don't know what are the solutions offered by the tool used, so maybe it is not that much easy. I could have asked my questions on vocal so that's on me too.
Yes, I'll really try to apply more TDD. Even for prototype. Lately I had to do some prototype to let other person tests functionalities of some hardware and the amount of time I lost at debugging those prototype was really frustrating.
Challenges to applying:
I'll need to practice in order to become proficient in TDD to keep up with it even when deadlines are approaching.
That was great to have an online working environment. Being able to focus on the exercise and not fighting against the tools was really a must.
Legacy code workshop:
Recommend to others: