TDD for Embedded C
2015-06-15 05:53:00 UTC
Most useful learnings:
How TDD can reduce the bug fixing time
Concepts v exercises:
Presentation v discussion:
One thing that bothered me a little was that the examples and exercises, that we saw and did, were quite small. I would have liked to see how does TDD stand up when the final source code file is above 300 lines of code. This is still a quite small file, but 3x bigger than we saw from the exercises. I noticed that the code to test lines where 1:3, one line of code vs 3 lines of test, so I would have liked to see how the test would have ended up when we have that big files. How manageable, changeable etc, would it be.
Noted in the "How can this course be improved?" question
The instructor was very good in presenting the material, he was very fluent and nice to listen too.
I could start tomorrow, but it would be very difficult. The project I am working in is in late state, so not so much implementations, but rather bug fixing. I could just take some simple file and start applying test to excisting files.
Challenges to applying:
I think the major challange is that not many people know/do this, so there might be some conflicts between ideas and how stuff should be done.
I really liked that it was organized very well, from the small things like parking your car, having lunch coupongs to the cyber dojo that helped to quickly transmit the theoretical knowlage to practical skills.
Legacy code workshop:
Recommend to others: