TDD for Embedded C
2018-09-07 18:14:19 UTC
Most useful learnings:
Interestingly, what I found most useful was not about TDD but about architecture design. Writing tests really forces me to understand the general idea and have a better design. Seeing other devs struggling with the same problems/thoughts I usually face was also comforting
Concepts v exercises:
Presentation v discussion:
It's not a big deal, but since I'm learning C++ I would have liked to use it instead of C. The idea is the same, but I would have learned about TDD and C++.
In some of them getting started was difficult. Maybe give ten minutes to get started and then a first explanation. After that everyone can continue by her own.
James is really nice person with deep understanding of quality software. It's not only about the presentation and the concepts, but also the *war* stories are enlightening.
Bring it on!
I can, what I can't do is encourage the rest of the team to do it. That will take some more time.
Challenges to applying:
TDD is a new capability that every developer has to learn, but they have to be willing to do it, to improve and deliver better code. In the project I'm working on I feel that they only care about the near future, not about what will happen with the product in 3 years. Introducing this concept to these people is not easy job.
The streaming was perfect, audio was clear, video too. I can't complain.
Legacy code workshop:
Recommend to others: