TDD for Embedded C
2020-11-13 15:07:57 UTC
Most useful learnings:
Unit Testing is more important than I ever imagined...
Concepts v exercises:
Not enough exercises
Presentation v discussion:
There are unfortunately only a few hours for the course so I understand the time for exercises are limited. However, I would have loved to see more opportunities for guidance in analyzing various problem statements (similar to buffer, scheduler and flash driver). They do not have to be exercises to the extent that we did the others, rather just walking through the process of 1) determining the required components/interfaces, 2) determining the required tests.
I don't believe the exercises requires any improvement per sé. However, there is no opportunity for deriving the interfaces and various tests.
Instructor was very knowledgeable, friendly and willing to assist.
Yes, although setting up the environment in windows for GCC proves to be tricky...
Challenges to applying:
Mostly time, although I understand that the long-term time benefits outweigh the time spent on the initial learning curve.
Pretty good. Low internet bandwidth is definitely a cause of major problems, but one can catch up fairly quickly having lost a few minutes.
It was truly a privilege learning from someone with the amount of experience that James brings to the table. Thank you for sharing your expertise in such a manner.
Legacy code workshop:
Recommend to others: