TDD for Embedded C
2021-07-17 00:36:49 UTC
Most useful learnings:
That it is possible to use all this knowledge in C legacy code with less chance of breaking it.
Concepts v exercises:
Presentation v discussion:
Concepts like the TDD small steps and mocks can be overwhelming for those who never experienced it. For example, the person I paired had a hard time with this concepts.
We paired two times. The first day was hard, the second was much better.
1) in the beginning, propose a really simple pair exercise that would not use any new technique other than the language itself. Just to know each other, get used to pair and the tools.
2) maybe a few words on pairing. many don't know how to do and will be just a "voyeur"
3) you used an expression for describing mocks something like: It will describe what functions your system must call. - this would be good to hear right in first contact with mocks.
1) at the end of the course, let the student download his dojo exercises (git versioned) so he can compare the steps with your demos and remember how to slice the tasks better. much of the struggle I saw was knowing how much to implement in each step.
2) the circular buffer had an structure that lead to quick understanding: you wrote the first tests letting us making it pass. I think the other exercises might have a couple like this.
James can speak directly to your soul. He points out solutions to deep problems you probably didn't even know you had.
He only uses jargon when necessary. James expresses himself in simple and polite language. You can feel that he has experienced the pain we feel today when having to maintain untested code and and managed to overcome these challenges.
Very nice and friendly person!
Bring it on!
I had to take three days, and a lot of work was waiting for me -- guess why? bad, LEGACY CODE makes the customers sad. and they will complain!
I was able to retake the work and will start tomorrow!
Challenges to applying:
To have the discipline of taking time to use it, and above all, to apply the discipline with someone that do not take time to learn. the person might even like what you say, but as soon as you move away, they start to write poor code again.
I think will have to write good clean modules to inspire them, and only after this, try to bring them to the TDD side.
I enjoyed very much! the tools worked very well at my side, and I don't mind having to wait for some fixes. This was a fun part for me actually, because I was able to participate more and feel like I'm a part of it.
Only for about 20 minutes the video was blurred, but the audio was very good.
Remote can be really boring. So I like when something unexpected happen. This gives reason for some laugh and interaction.
People do not seek each other to talk or to exchange any information as in person events.
Legacy code workshop:
Recommend to others: