TDD for Embedded C++
2018-09-28 19:03:47 UTC
Most useful learnings:
Baby step! I've taken a TDD class before, but this time we really focused on what it means to take small steps, both conceptually and practically with hands-on exercises.
Concepts v exercises:
Presentation v discussion:
I don't feel that the slide-deck was used to its fullest potential. The big thing seems to be that we skipped around a lot through the slides, which certainly good use of our time, but it makes it hard to know which slides are worth going back to, and which are not.
My off-hand recommendation would be to add some form of hierarchical organization to the slides, take a few moments to discussed the organization in class, and point out why we are skipping over certain sections.
Not your problem, but better synchronization in cyber-dojo would improve the pair-programming experience.
Very impressed and happy with the course. James did perhaps ramble on a few points, but not enough for that to be an issue.
Bring it on!
Kinda. Ironically my next project is in C#, and I don't have a good nunit infrastructure setup... will do that though.
Challenges to applying:
Poorly written legacy code, poorly tested legacy code, and just generally legacy code.
Legacy code workshop:
Recommend to others: