• Course: TDD for Embedded C
  • Date entered: 2021-11-05 09:08:32 UTC
  • Course rating: Good
  • Most useful learnings: - Schedule pressure initially increases the feature velocity, but then has the opposite effect through poor code quality and increased defects (slow down to go fast) - Bad code should be improved incrementally (one verifiable step per increment, it is easier to keep a system working than to fix it after you break it) - Unit Tests: Just using C with classes of C++
  • Concepts v exercises: Good balance
  • Presentation v discussion: Good balance
  • Course improvements: - I didn't quite understand the purpose of this live coding in the second part of the session. I saw the point in the first part to prepare us for the exercises but watching you have compilation errors and linker erros again and again in the second part I didn't understand. - I missed a schedule for the day
  • Exercise rating: Very Good
  • Exercise improvements: In my opinion, the exercises were very well prepared and I do not know what can be improved.
  • Instructor comments: Good explanations, but sometimes digressed too far from the topic.
  • Better prepared: Much better
  • Start tomorrow: Yes because there is no impact on our SW process
  • Challenges to applying: - Making colleagues aware of the benefits of TDD - The current toolchain is quite slow. Fast feedback is needed to apply TDD efficiently
  • Other comments: -
  • Legacy code workshop: No
  • Recommend to others: Yes
  • Quote permission: No