Course:
TDD for Embedded C
Date entered:
2016-08-23 14:17:31 UTC
Course rating:
Good
Most useful learnings:
TDD can cut down on Bug fixing cycles by integrating testing into the code generation part of the design.
Concepts v exercises:
Too many exercises
Presentation v discussion:
Good balance
Course improvements:
Day 2 was horrible, and I don't know what could fix it. If Tom hadn't already been to your course and been through it, I would have probably written TDD off on that day.
Exercise rating:
Good
Exercise improvements:
It's too easy to get bogged down in the small details of the exercises and waste time. I think it might be better to do individual exercises on the last day of class. All other days we should do the exercises together so that we can get some hands on experience while ensuring that things are moving along.
Instructor comments:
The instructor was very vigilant about making sure people were making progress. This was appreciated.
The instructors teaching methods just didn't make it easy for me to learn. I appreciate a traditional method where you "tell me what you're going to tell me", then you "tell me", then you "tell me what you told me". But that's just me.
Better prepared:
A little
Start tomorrow:
No. Too many deadlines.
Challenges to applying:
Finding time.
Other comments:
Remote delivery was GREAT!
Legacy code workshop:
No
Recommend to others:
No
Quote permission:
Yes