TDD for Embedded C
2020-09-10 22:54:13 UTC
Most useful learnings:
Applying the Crash - Pass algorithm to legacy code. I'd done something like this before (once or twice, as a toy/research example) with some anxiety whether I was even achieving anything in the process. This was great.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
Too much presentation
I'd recommend looking for ways to break up and alternate the presentation/exercise components into shorter cycles: the presentations are thorough and patient and generally great, but there's a lot of information to process and by the time I reached the exercises on the final day, I was definitely experiencing serious brainfade!
James is great! The supporting media + PDF materials are nicely prepared, the delivery is clear and thorough, the active supervision in the exercise components was really helpful and impressive.
No. The current projects are in a winding-up phase. But I'm prepping for the next one on the sidelines, and aspects of this approach are definitely going into the planning.
Challenges to applying:
Third-party integration and sheer volume of legacy code.
Legacy code workshop:
Recommend to others: