TDD for Embedded C
2016-10-10 08:07:06 UTC
Most useful learnings:
It should not take much longer to develop code using TDD. Especially in large SW projects. Growing code takes longer and longer to test.
TDD can be learned ;)
Concepts v exercises:
Presentation v discussion:
Too much discussion
It was a bit confusing sometimes working at the exercises and beeing interrupted many times. I think it would be better if you give some fix time slots for the exercises.
+ Very interesting stories. You have a huge knowledge of the whole stuff and I think that was the reason I learned quite a lot in only three days. Thanks a lot.
- If you explain something for one person it may be better to connect you and the person directly if this is possible. I found it quite annoying when doing the exercises.
No not really. I have to practice TDD much more first. Also we have to think how we could start in our company...
Challenges to applying:
time pressure, a huge amount of legacy code (some is very old and poorly programmed), have to convince the management of TDD
Legacy code workshop:
Recommend to others: