Course:
TDD for Embedded C
Date entered:
2017-10-02 19:33:47 UTC
Course rating:
Very Good
Most useful learnings:
Most valuable aspect was being able to actually write tests and code. Getting the setup done was a big hurdle out of the way of doing TDD.
Concepts v exercises:
Good balance
Presentation v discussion:
Good balance
Course improvements:
A little bit more focus on legacy code and maybe keeping one section where everyone can look at their own codebase and write tests for one function. This will be super useful in terms of being able to get started with TDD on our own code. The first step from the 'herculean effort' that is needed to get the legacy code in good shape.
Exercise rating:
Excellent
Exercise improvements:
Both the exercises were pretty cool. Got to learn new concepts.
Instructor comments:
James was great. He handled the class well. Cracked good jokes and kept everyone awake :D
Better prepared:
Much better
Start tomorrow:
Probably. It's easier to continue than to start and, thus, having a section in the course where you 'start' will be great.
Challenges to applying:
All working people have tasks assigned to them already and have to put in a lot of extra effort to do work to just improve codebase by applying TDD. While most teams will support that there is always a priority to follow and such improvements can get sidestepped.
For me personally, we are going to move to a different chipset soon and will be wrapping up the current FW. I'm wondering whether it'll be worth to put in effort to improve this legacy code or just start the new one with TDD. I also want to see if I can follow the path of abstraction and change this code to try and work with any processor. I'll probably shoot an email to James about this.
Other comments:
Good venue. Good food. :D
Legacy code workshop:
Yes
Recommend to others:
Yes
Quote permission:
Yes