TDD for Embedded C/C++
2021-12-02 08:07:26 UTC
Most useful learnings:
Well, most of the concepts I've learned I did already by instinct the one or other way. What I learned is how to do it right.
Concepts v exercises:
Presentation v discussion:
Hm, the only thing I can think of which I feeled a bit tiring was the demonstration at the end of the last day how to get some sources buildable. Actually this is my daily work and I think this of my colleagues as well. Maybe it would be a good idea to ask after 10 minutes demonstration if everybody got the point already before continuing for 30 or 40 minutes.
For me they are good as they are.
Very skilful, patient, accomodating, adaptable to the specific problems of the trainees. And a very good understandable English which is very important for non English mother tongues.
Yes, as I've already written I used most of the learned concepts already by instinct at least somehow. Now I know how to do it right and consistently.
Challenges to applying:
Unfortunately I've almost never the luck to write a software on my own from scratch. Instead I usually have to adapt mostly very complex 3rd party sources to our requirements. I've learned how to use TDD there as well. Constant refactoring is an important concept of TDD and actually it almost always itches me to do so also with used 3rd party sw. Problem with this is that it makes often required merges of new deliveries much more difficult up to impossible. So refactoring is not always a good idea. But this of course doesn't prevents me of at least adding testcases for the things I have to change or add.
Legacy code workshop:
Recommend to others: