TDD for Embedded C
2019-12-13 09:00:18 UTC
Most useful learnings:
I had about no knowledge on TDD before starting the course. A new world opened to me, made of a brand new programming technique and point of view wrt debug, tests, and coding. TDD is powerful because coding is powerful.
Concepts v exercises:
Presentation v discussion:
Too much presentation
I would reduce the first presentation part. I would reduce the overlapping with the book, giving it a more practical footprint, because the book reading can be done in advance (and shall be suggested to the trainees as a base for properly face the training), while the training shall deal with an additional value wrt the book.
We didn't have much time for exercises. I mean the exercises where fine and mandatory to understand the matter. Also IMHO they represent the value added to the sole book reading. But I would want to complete them for practice, but there was no time instead. maybe cutting off some of the presentation on initial training phase would provise some room for more exercising.
This is because starting the exercise took a bit (for me) to understand the matter and start thinking in TDD mode.
Very skilled in coding, it is always good to have a senior programmer teaching you golden rules involving the stuff you do every day but that you usually don't have time to learn how to improve.
Bring it on!
I would like to, but I can't. Because it does not depend on me, but on my superior will to apply those practices. And he depends in turn from people who need to sell the product so I may not have time availability to train my team colleagues and not have time for TDD warm-up, which will take a bit. If it depends on me, I would start applying TDD tomorrow. I may start next week then.
Challenges to applying:
As said above. We are often in a hurry to deliver, and we have not much time to start with brand new techniques
Legacy code workshop:
Recommend to others: