TDD for Embedded C
2018-08-31 01:13:24 UTC
Most useful learnings:
that TDD is a development process and not a way to verify software.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
I felt like the value of TDD is learned through experience, so I saw more value in those than the discussions.
I would have liked to have had an exercise that let us do a refactor all together and talked about it.
The instructor seemed well-versed on the process of TDD, but seemed to be resiliant and almost defensive at times when the process was criticized. I think the issue was that those who were dissident were not fully understanding the process, as I myself was one initially. Once the process was understood, a lot made sense. So I would encourage the instructor to be more encouraging.
Challenges to applying:
Biggest issue that we have is that our code already has very very specific tests that are laid out in documents describing what those tests should be, so modifying code would also modify the test cases according to a process. This goes against TDD a bit.
I think that I would have liked it if the third day was less of looking at one thing as a group and more of breaking out like day 4.
Legacy code workshop:
Recommend to others: