TDD for Embedded C
2018-03-28 17:13:08 UTC
Most useful learnings:
-TDD improves quality and speeds up development.
-It makes fun testing with this technique.
-It documents code, or at least the understanding that the developer has of what the code should do.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
-I would have liked more practice and less presentation in the time balance.
-I would have liked to learn more tachniques about how to mock up peripherals.
-I would have liked to practice to set up the environment to perform tdd
-One single type of example that evolves from exercise 1 to exercise N would have help to understand the tdd techniques better.
-More practice on them would have been nice.
-I had the feeling the pace was too fast sometimes.
-Very pleasant and clear way to present things.
-Class very well prepared.
-I am not confident with the set up of the tdd framwork to my current projects. I have for instance no experience with make files.
- Time pressure to deliver does not allow me to invest as much time as required to set up tdd on my current projects.
Challenges to applying:
- I think to set it all up. Surely there is a learning curve to apply tdd as well. We just got a taste of the possibilities with the seminar. The manager understand the need of all this, anyway. In our case that facilites.
I find your teaching style, James, is very informative and pleasant. However, sometimes I had the feeling that some accessory things were dedicated too much commenting. These accesory things could be explained in less time. Example: what people liked/not like about software.
I would have appreciated a slower pace when explaining what was required in the exercises.
I personally did not like so much that being a course on embedded C it was plenty of references to object oriented languages.
Legacy code workshop:
Recommend to others: