TDD for Embedded C
2018-01-19 02:11:49 UTC
Most useful learnings:
That it is very, very important to do the development in very small steps not just because it speeds up the microcycle and limits the mistakes you can make, but also because it allows you to verify that each test can both fail and pass. It gives you confidence in the tests.
Concepts v exercises:
Presentation v discussion:
No comment on how to improve. I loved the use of cyber-dojo to allow us to all work on the same thing, in teams if desired, with the instructor being able to remotely check our work.
Really good instructor overall. Spoke clearly and logically. Presented ideas with reasons behind them. One suggestion is for the instructor to make sure he is understanding/answering the question asked. Perhaps it was because we didn't know the terminology to ask what we were really trying to ask but sometimes it seemed like the answer assumed we were asking something we weren't.
Challenges to applying:
Huge code base of legacy code, not designed for testability. As far as applying to new code, we still need to solve a lot of issues with the structure of our code base that does not easily support testability.
Legacy code workshop:
Recommend to others: