TDD for Embedded C++
2018-11-29 21:03:20 UTC
Most useful learnings:
Make the test fail first and then make it work, this was a very novel approach.
The process allows your code to go from more specific to more generic.
Find series of small verifiable steps, to move forward, and make the code work on purpose.
Concepts v exercises:
Presentation v discussion:
I was thinking there were times, when we were doing refactoring, live. Every time we do anything live there is a lot of time we end up spending in the mechanics of doing the refactor, like missing declarations etc...
I was thinking it would have been more productive to have a refactored example and showing the before and after side-by-side, and then may be have a refactoring exercise.
Doing this class remotely, does make it a little difficult to follow especially when we are doing exercises. Doing it in a class-room would have been more productive for the overall class.
Subject matter expert, well prepared for the presentation, Eloquent and organized.
Challenges to applying:
My workplace does promote this approach. I think the biggest challenge for me will be myself.
I have written thorough (or at least I thought they were thorough) unit-tests in the past. However the whole iteration of "fail test first, write code to PASS the test & PASS the test", does seem painful. I will have to give this is a try, I am afraid in getting through the mechanics of making my code PASS the test do I ever loose sight of the big picture.
I was thinking at end of each day if we had a couple of slides that talk through the summary of what was discussed that day for e.g. key takeaway for that day, it would help solidify the ideas and help us feel a little less overwhelmed.
Legacy code workshop:
Recommend to others: