Course:
TDD for Embedded C
Date entered:
2017-02-13 14:42:00 UTC
Course rating:
Very Good
Most useful learnings:
The importance of doing as little as possible and not jumping ahead of your tests. Specifically for the reason that you write untested code that way.
Concepts v exercises:
Good balance
Presentation v discussion:
Good balance
Course improvements:
Exercise rating:
Very Good
Exercise improvements:
Instructor comments:
Better prepared:
Much better
Start tomorrow:
Yes, since we are already in the process of moving to an improved code base.
Challenges to applying:
Mainly the support and buy-in from fellow developers. Some think there is no purpose to TDD. Some like it, but think it takes too much time. Others like it but don't think our management/sales force will accept the added time needed to make tests and deliver a tested product first then a slightly buggy product.
Other comments:
I'm a fan of testing, but not all my co-workers are. You mentioned a couple of times that you can't convince us and that we'd need to convince ourselves. It would be nice to have compelling data ("hard facts") that show the trend of improvement that testing brings to an organization. The closer the data is to embedded development, the better.
Legacy code workshop:
Yes
Recommend to others:
Yes
Quote permission:
Yes