TDD for Embedded C
2020-03-17 09:11:43 UTC
Most useful learnings:
That TDD can make you a lot faster. That it is a way for me to be more structured about my work - it gives me a good reason to be.
Concepts v exercises:
Presentation v discussion:
I think the course is very good as introduction for TDD, but I would like to see some more advanced topics covered (e.g. an example where thread safety is a concern). It would also be nice with some more coverage on QA in general and how we achieve a satisfactory quality of the whole product with different kinds of testing and other QA mechanisms. This would make it easier for me to see where I can use TDD to improve and spot other areas where we may be able to improve in relation to QA.
I like that he is very chill with a good sense of humor and clearly knows his stuff. Also good at keeping focus on the important parts and not spending too much time on things that are interesting but not relevant to all course attendees.
Sometimes it can be a bit hard to deduce whether he understood an attendee question or not, so spending a bit more time talking about questions from the attendees in general might be better. This could be done by asking if other people had similar questions, asking about the context and just increasing the interaction with the crowd a bit.
Bring it on!
Yes! I have already been doing it, now I'm ready to do it even more.
Challenges to applying:
Previously it has been an issue that not all members of the team have been familiar with TDD. Now all members of the team have attended the course and should be much more ready for it.
We have legacy code, where it is very hard to introduce TDD. It can be hard to find the balance between maintaining old stuff and creating something new based on current knowledge.
Legacy code workshop:
Recommend to others: