TDD for Embedded C
2017-10-02 15:31:43 UTC
Most useful learnings:
The philosophy and design considerations behind of a Test Driven approach to embedded C.
Concepts v exercises:
Presentation v discussion:
I think the course would benefit from a stronger schedule/syllabus. Being able to address tangents and free-form is important, but I think too much of it blunted the overall impact/coherent message of the course.
Had some synchronization issues with Code Dojo, but appreciated being able to jump straight into a working environment.
James is obviously an expert and wealth of knowledge as an instructor, glad to have learned this from him. I do wish that I had attended a running where he was not quite as jet lagged and distracted by construction work going on at home.
Not tomorrow, because I need to change my build system to accommodate the test builds.
Challenges to applying:
Our engineers are not dedicated software/firmware engineers. Organizationally, this leads to a weak understanding of how to successfully manage and coordinate software and firmware projects (myself included). No build system/CI infrastructure currently in place to support TDD.
Legacy code workshop:
Recommend to others: