TDD for Embedded C
2016-06-03 17:56:23 UTC
Most useful learnings:
I understood the importance of TDD but never really felt I could "sell" it to people outside of software development. Now I don't think I can code WITHOUT it which makes selling TDD exponentially easier!
Concepts v exercises:
Presentation v discussion:
The course work prep could be greatly improved. Helping students/clients understand the process you'll be taking them through would make a massive improvement on absorbing the material. When we started I wasn't sure if we should be interacting with the examples while you were introducing the concepts/exercises. Since this was not in person we are able behave in ways that a more traditional setting wouldn't allow. This has benefits & draw backs. The benefits are around the ability of the presenter & audience to take what ever breaks they deem reasonable. You could take a lunch break when you knew we were all engrossed in an exercise & we could use our time as we saw fit (go to the bathroom, handle personal calls etc) without interrupting the information. That allowed us to step out when we felt comfortable.
But when you were introducing the exercises I felt like I was supposed to be making modifications at the same time. Thus I was having a hard time following everything you presented.
To be frank I am not sure. The exercises seem pretty solid and I wouldn't change anything here.
Don't ask for a show of hands when no one is physically present. Minor issue really.
Bring it on!
Yes and when I didn't I felt like I was violating some moral code.
Challenges to applying:
Very few really. Our manager is not only excited about TDD he is backing the developers to other segments of our company.
Push your book! It's well written and could help attendees as a quick reference as we all start implementing TDD. Thank you for taking the time to share your passion about TDD with the world.
Legacy code workshop:
Recommend to others: