TDD for Embedded C
2018-10-03 19:14:48 UTC
Most useful learnings:
How small of steps to advance in to keep the TDD feedback loop going. To keep code compiling and tests passing during refactoring (rather than breaking code during refactor and fixing it back to working state) - including adding duplicate logic during refactoring rather than extracting code into logic directly.
Concepts v exercises:
Presentation v discussion:
Possibly break more often early in the exercise to review.
It was really fascinating to hear in person the perspective and advice of the person who literally wrote the book on the subject.
Bring it on!
Yes, have a good understanding of the fundamentals.
Challenges to applying:
Untangling tight dependencies within the codebase (including on static data). Dealing with modules that include both direct hardware register access and business logic.
Legacy code workshop:
Recommend to others: