TDD for Embedded C++
2021-12-21 12:25:04 UTC
Most useful learnings:
The purpose of the tight loops, i.e. to ensure the tests will FAIL when they're supposed to.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
I think a little more time spent doing exercises would be beneficial, as that's how most of us learn.
Taking the first step on some of the exercises was often the hardest part, and we spent a fair amount of time "stuck" on that. Anything that would've helped us get moving on our own would be useful.
I think the chosen exercises, though, were excellent. I'm sure there's been much thought put into creating exercises that are familiar, but also provide teaching value as well as an opportunity for a-ha moments.
I clicked very well with James, as it's evident he and I think alike.
We started a few years ago, at least some of us. For me, this was an opportunity to fill in some blanks about WHY, and James certainly did that. But most of my organization has not been exposed to TDD, and I think it was a good start. Unfortunately, I got pretty limited feedback from other colleagues in the class, but the little I did get indicated there wasn't quite enough time to cover the material.
Challenges to applying:
Without a doubt, getting everyone on board.
The separation between Cyber Dojo and Gather Town was not apparent to me until the second day of class, and I was implicitly assuming there was a connection there that didn't exist. Splitting into separate rooms was both good and bad. Once engaged in an exercise, it was difficult to get the instructor's attention until he happened by. I was expecting a more Teams-like experience where we could raise our hands and be called upon while we were doing exercises.
Legacy code workshop:
Recommend to others: