TDD for Embedded C
2018-01-11 21:28:35 UTC
Most useful learnings:
Single most useful is that I can separate manufacturer's IDE from a test framework easily. Will be diving in on new code and fearlessly refactoring some legacy code.
Concepts v exercises:
Presentation v discussion:
Hard to improve without spending more time ($$). Perhaps a follow-up session in a couple months would be useful.
They are fine. Hard to fit every situation. There are no silver bullets that fit all situations.
You won' make as much money as a comedian.
Somewhat. Have near-term deliverables with a legacy system. On the bright side, have a new project just after that.
Challenges to applying:
Fighting Manufacture's IDEs. Hardware is.
Could focus on refactoring in a future session maybe. That could be big with the legacy code base.
Legacy code workshop:
Recommend to others: