TDD for Embedded C
2016-06-09 19:06:51 UTC
Most useful learnings:
Seeing you refactor the LightSceduler from single event to multi events while keeping the single event code in there until the multi events code was all in place. Don't break the code until you have something new to stand on.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
I have read your book and also parts of other books about TDD. This means I am familiar with lots of the theory. What I really need is lots of practice including feedback. So I would have liked even more exercises. But I realize that you have to create a course that fits people with different background. Also it was good to hear the theory again of course since it was a while since I read the book.
Don't know. I think they were good.
No comments, was good.
I can start tomorrow. I guess the key is to do it step by step.
Challenges to applying:
We are three different sites working on the same project. Each site is in a different country. Our site has some of this stuff in place already (unit tests, automated integration tests). We still have lots of things to improve. But the other sites work with manual testing only. So each site has a different way of working but we depend on each other very much. The other sites do not care if our Jenkins server go red because the cannot even access it. We should probably fix that.
I think the technical setup was great, i.e. Webex for presentations and Cyber-Dojo for exercises. It would have been even better if we all had enough bandwidth to run video all the time. I think the Cyber-Dojo setup is a great tool for working together with code like this.
Legacy code workshop:
Recommend to others: