TDD for Embedded C
2019-08-16 17:10:00 UTC
Most useful learnings:
Refactoring approaches in C.
Concepts v exercises:
Presentation v discussion:
Too much presentation
There was a good amount of time spent on exercises, but I think things could be improved through more participant reflection on the exercises and discussion. The remote nature across many time zones may have inhibited this however. Also, the participants in India that had to leave an hour early broke up the flow of the course. I'd suggest having some maximum allowed time zone band and doing separate sessions so that there is not a 12 hour differential.
The exercises were very good. I'd suggest finding some shorter exercises or cutting up the existing exercises into smaller pieces to break up the blocks of presentation time. I think some expert feedback on 1-2 exercises after completion would be beneficial as well. Walk through them and show everyone what someone did well and what they can improve on. I'd also recommend take home exercises that could be reviewed at the beginning of each day to give additional practice.
Very knowledgeable and patient. Kept cool when there was a frustrating portion with cyber dojo setup and remote participants were not responding to questions over zoom.
No. I'm a unique case in that I have significant experience with TDD but am lacking in embedded knowledge.
Challenges to applying:
Majority of our engineers do not know embedded development. However, they are already doing TDD.
I felt the green screen really improved the remote delivery. I'd keep that and work on incorporating the suggestions from the other student that was knowledgeable on green screens. See my suggestion above on time zones.
Legacy code workshop:
Recommend to others: