TDD for Embedded C
2016-11-09 19:03:47 UTC
Most useful learnings:
The incremental way to develop by creating simple tests first, then implement only enough of a solution to pass the test, then create more complex tests, etc.
Concepts v exercises:
Presentation v discussion:
Too much presentation
A little less lecture and talking about tangential topics, and more focus on the core information of the course. More time on the HW mocks would be good, as that is a really big area for most embedded systems. Also, some presentation on how to implement when doing cross-platform development.
Entertaining and enjoyable to listen to. He obviously knows his stuff and is an expert in the field (as are all Barr Group affiliates).
No. The learning curve is too big, and my existing workload is too great to allow the time I need to start to implement. I have to look for the right project to try it out on.
Challenges to applying:
Getting buy-in from my manager that the extra time now is worth it. It will be easier to do it at the beginning of the next project, not now near the end of the existing project and the hard deadlines we are facing.
2 full days was enough. I don't think I would have been as engaged if the class extended to 3 days.
Legacy code workshop:
Recommend to others: