TDD for Embedded C
2016-08-15 15:51:50 UTC
Most useful learnings:
The most useful thing I learned was that there is already a clearly-defined series of steps to go through from unit-testing plain C to TDD with embedded code.
Concepts v exercises:
Presentation v discussion:
One thing I missed -- perhaps it was covered -- was that different authors use different terminology for testing. So words like "mock", "fake", "spy", etc are overloaded.
The material is great. Having folks pair up throughout the exercise would make it better, but I'm not sure how you do that with an online course.
James did an awesome job! It was like having him here in the office helping out. He was very responsive to questions and took his time to explain concepts that might have been difficult to grasp.
Bring it on!
Challenges to applying:
As an instructor myself, I cover so many topics that by the time I get back to this topic, I'm likely to be cold on it.
I have never taken an online, live course that involved programming, and I was somewhat skeptical the first day. I quickly found out that by combining a normal video conference with virtual machines in the cloud, the instructor was able to both give traditional classroom training and check in on students as we worked through the problems. There was even a mechanism for students to be identified by animals -- so that if the class decided to discuss one piece of code, the student wasn't put on the spot. Both highly enjoyable and useful.
Legacy code workshop:
Recommend to others: