TDD for Embedded C++
2018-11-08 23:27:42 UTC
Most useful learnings:
Touching on concurrency while reviewing SOLID and design patterns.
"Resist the batch."
Concepts v exercises:
Too many exercises
Presentation v discussion:
If our code wasn't so bad the coding exercises might be more enjoyable (in other words, it's no the courses fault).
I would like to have focused more on the design principles. It might be interesting to take one of your already existing examples, written in a "bad" way and perform refactors. Currently I spend almost all of my time in legacy poorly written code and just a little bit working from the ground up.
Yes. Already doing TDD to the extent possible on new and existing code.
Challenges to applying:
Spaghetti. Ancient infrastructure. Difficult to maintain infrastructure.
To be honest as a course repeat it was very valuable to reiterate ideas, techniques etc. The first time everything was new and it took a few years of hard practice to really appreciate the core philosophy.
Legacy code workshop:
Recommend to others: