TDD for Embedded C
2021-12-03 08:37:56 UTC
Most useful learnings:
My significant learning is not about TDD itself but about humans. Obviously keeping one's habits is quite common. But to my surprise even some of my really experienced colleges did not even get the point of TDD. "Too much TDD for us" was one of their comments. I ask them whether they what to do some kind of 50% TDD instead and what the hell this should be. In the end it means they will do no TDD at all.
So my job for the near future will be to convince them that we need more tests and that this will never happen without TDD. And that TDD is possible even for our code basis. Fortunately I have a meeting platform where I can show examples on a regular base.
Concepts v exercises:
Presentation v discussion:
Send information about day 4 more early. This went bloody wrong. Nevertheless we managed day 4 in a sufficient manner.
No idea. I really liked them.
No. But just because I will be busy with non-programming stuff.
Challenges to applying:
Convince the team that we need automated tests.
Legacy code workshop:
Recommend to others: