TDD for Embedded C
2017-10-12 22:01:01 UTC
Most useful learnings:
The course taught me to slow down and really think about the code and the areas that it can fail. The "red-green-refractor" should be part of my workflow when coding.
Concepts v exercises:
Presentation v discussion:
I would like to see additional simple exercises like the circular buffer. This would help me with the red-green-refractor concept.
I felt the scheduler exercise was too long for me. I didn't finish it. I would prefer more smaller exercises.
James is an expert at tdd. You would expect this since he is related to Uncle Bob. James was a bully at times if he thought you were flailing in the exercise. Too many Reds or Yellows got you into trouble. But in retrospect, he was only enforcing the tdd way. James had an excellent delivery and could field all the questions in the parking lot.
Yes, my next project I will start using tdd.
Challenges to applying:
Time schedules. Legacy code. Team members may not be on board with tdd. Platform issues with CppUTest or other testing framework.
This was my first Webex training. It was good. I would prefer a modified training of 1 day or 2 split days. Three days seemed a little much for me.
Legacy code workshop:
Recommend to others: