TDD for C
2020-03-27 01:02:28 UTC
Most useful learnings:
That TDD is done in small iterative steps. Before the course I thought TDD involved writing all test cases before developing any production software. This has taught me that there's a need for a fast feedback loop for tests and production software development.
Concepts v exercises:
Presentation v discussion:
The refactoring video has large portions of it where the audio is very poor. Every time you walked to the board in the video the audio became almost impossible to hear.
It took me a bit of time to find the flash driver flow chart in the slides .pdf before working on it. If there was a way to put that in the cyber dojo instructions it would make it faster to get started.
Yes. We've already got a unit test framework setup using google test/mock. I'm going to try applying the concepts from this course in my next sprint.
Challenges to applying:
The feedback loop between unit tests and production code is a little bit long.
There were some issues with the screen bouncing around on day 1 but it was fixed for the next day.
Legacy code workshop:
Recommend to others: