Course:
TDD for Embedded C
Date entered:
2015-02-19 16:26:11 UTC
Course rating:
Very Good
Most useful learnings:
Using unit tests as a way of organizing and validating your code as it was being written, rather than writing code from your set of requirements and then unit testing it later only to find it laced with bugs. Also an intro on how to properly mock/fake functions out for unit testing will go a long way.
Concepts v exercises:
Good balance
Presentation v discussion:
Good balance
Course improvements:
Maybe more time to work on the exercises to ensure that everybody can finish them? I understand this was probably limited by condensing the course into a two day period.
Exercise rating:
Excellent
Exercise improvements:
N/A
Instructor comments:
Very engaging instructor. Did not spend too much time on slides explaining the concepts. Instead gave a slight overview of the topics, then jumped into examples, and then let us practice the exercises. This is a much more effective learning practice rather than just throwing slides at people, so I enjoyed that.
Better prepared:
Much better
Start tomorrow:
I cannot start tomorrow, as I am working on some system based work right now (Interprocessor and threading communication), so a unit testing approach doesn't make much sense in this work. But in the near future I'll be working on true feature development that is a little easier abstracted from the system, so I look forward to using TDD on this work.
Challenges to applying:
Lots of code that has already been written, so lots of stubs/fakes/mocks may need to be written to move development off target.
Other comments:
N/A
Legacy code workshop:
No
Recommend to others:
Yes
Quote permission:
Yes