TDD for Embedded C
2015-11-13 11:59:40 UTC
Most useful learnings:
VERY small steps during the write-test fail, code, test pass cycle
Exploding Mocks. Difference between mock (expectations) and stub/fake.
Concepts v exercises:
Presentation v discussion:
I can't think of any obvious improvement.The Dojo exercises are very good. And the method of James' tidying up each step and we all re-start from the same place each time. Prevents people getting further and further behind. Also James' monitoring of our progress remotely and then targetting people to help them is excellent.
Very good. Concise, experienced enthusiastic professional engineer who knows the world we work in, and who is very good at getting new concepts across. Also a fun personable guy!
Challenges to applying:
Buy-in from management. Technically we can do it, and I am convinced we should. I think we may move slowly towards this method - possibly to go hand in hand with Agile, if we could adopt that. That hurdle is the biggest to climb since requirements capture is a big issue for us.
Legacy code workshop:
Recommend to others: