Course:
Test-Driven Development
Date entered:
2012-02-03 02:09:13 UTC
Course rating:
very good
Most useful learnings:
Techniques for testing code.
Testing code not only ensures that it works; but ensures that it's cohesive.
Concepts v exercises:
good balance
Presentation v discussion:
Good balance
Course improvements:
It would be great if we could set up a project that built the final production code with the vendor's compiler. There's way too much risk for a beginner to break the production code.
Exercise rating:
very good
Exercise improvements:
Although some of us could not finish the exercises in time; it was great that we could go to the next step with a fresh project.
Instructor comments:
Excellent teaching style.
Better prepared:
Much better
Start tomorrow:
Yes. we now know the tools and techniques for TDD; it's just a matter of refining them.
I don't know if anybody was able to build multiple targets (PC test & production code) in one build. This must happen before we can dive in and trust production code tested on the PC.
Challenges to applying:
"There is a lot of work to do to catch up with legacy code. Most legacy code is hard to test; it needs to be re factored. Yet we should have tests before re-factoring. ""Chicken or the egg?""
Preparing the tools for TDD and getting more experience with them is going to be a big challenge in the beginning."
Other comments:
Follow up training will be important; without it some might loose motivation for TDD. I greatly appreciate your offer for others to attend the workshop portion of the next course at SKK.
I wish I had more time to think about my comments :)
Legacy code workshop:
Yes
Recommend to others:
yes
Quote permission:
yes