TDD for Embedded C
2017-03-02 14:59:02 UTC
Most useful learnings:
"Have you got a test for that?" TDD will make my life easier, its not scary, it is my friend.
Concepts v exercises:
Presentation v discussion:
A 15 minute break in the middle would be nice. Or maybe 2 10 minute breaks. This would allow everyone to stretch legs, grab a snack, use the restroom etc. I was able to run away from my desk a few times to do these things during the exercises, but I did not want to miss out on anything. If everyone knew the break was coming they could relax a bit more and focus. Then they would come back from break in a better position to focus.
I do not code in C every day. For me it would have been nice to have the exercise on the second day be simpler, so I could focus on the TDD principles and not panic because there was a C programming concept I was struggling with. Or maybe keep the examples the same but jump in more often when you see someone floundering. You did do this when I asked for help (thanks). Sometimes people are too self conscious to ask for the help.
It was great. I can never go back to not doing TDD. It will take me a while to get good at it. But I am determined to do it.
Yes, as you taught us, incrementally and methodically.
Challenges to applying:
Getting good enough at it, that I can evangelize the practice. I won't have a problem getting it adopted if I can lower the barrier for entry to others. I will be recommending your class to others that we will be hiring soon.
Cyber-dojo was perfect. Watching you do the refactoring was the real clincher on why I MUST do TDD. You also shared several bits of wisdom from your years of programming (this was like gold).
Legacy code workshop:
Recommend to others: