Course:
TDD for Embedded C
Date entered:
2018-10-29 11:03:47 UTC
Course rating:
Fair
Most useful learnings:
As we already write tests, not much. The most useful must be that there was nothing presented which would cause big concerns that we do something wrong/bad.
Concepts v exercises:
Too many exercises
Presentation v discussion:
Good balance
Course improvements:
What is a good test and how to create them should be more emphasized.
Exercise rating:
Poor
Exercise improvements:
There was too much time spent on small changes to code which should have been used in better way.
Instructor comments:
Better prepared:
Not at all
Start tomorrow:
I already write unit tests but the way how it was presented raises concerns in me. Especially the amount of time spent on constant reworking of a solution where I know before I start writing it that it isn't working at all as a final solution. I know code can and should be refactored, but it should be done only when needed. By the small step increments and the "don't write more than needed to pass the test" guideline the refactoring happens way before it is really necessary.
Challenges to applying:
I don't agree with the way how it was done during the exercises.
Other comments:
Legacy code workshop:
Yes
Recommend to others:
Only if improved
Quote permission:
Yes