• Course: TDD for Embedded C
  • Date entered: 2021-12-06 11:39:38 UTC
  • Course rating: Very Good
  • Most useful learnings: I learned a lot. Here are 3 important points: - Hardware / target is the bottle neck; Debugging / troubleshooting on the target in a large monolithic software block takes much longer than in a TDD environment - I got to know a new TDD environment, before that I was familiar with cmocka / valgrind - I have seen that the software complexity has to be kept as small as possible in a TDD environment
  • Concepts v exercises: Not enough exercises
  • Presentation v discussion: Good balance
  • Course improvements: For me as a non-native speaker, the fast language in the videos was a problem.
  • Exercise rating: Good
  • Exercise improvements: More time for the exercises. Especially on day 2, the workload was not even rudimentary.
  • Instructor comments: -
  • Better prepared: Much better
  • Start tomorrow: From a technical point of view, you could start right away. However, our internal project organization does not allow this. That would cost a lot of time and money at first. Note: In my career there have been projects in which a large part of TDD development has been done, e.g. DSP software for the NodeB. The reason: With 100 percent code optimization on the target, debugging was not possible. We had to simulate everything beforehand. My experiences with it are technically absolutely positive. However, an appropriate organization in the project is essential.
  • Challenges to applying: However, an appropriate organization in the project is essential.
  • Other comments: However, an appropriate organization in the project is essential. The problem: Project management usually wants something different.
  • Legacy code workshop: Yes
  • Recommend to others: Yes
  • Quote permission: Yes