TDD for C
2020-11-13 05:13:14 UTC
Most useful learnings:
1. There will be bugs while writing code but it can be fixed easily then and there with the TDD.
2. The production code should be modular and written in small functions so that it can be tested fully.
3. Untested code should be removed as quickly as possible.
4. Comments should be put to describe "why" rather than "how".
5. Development can be started and tested without h/w.
Concepts v exercises:
Presentation v discussion:
May be before starting the exercise, the functions/files being used are explained a bit better. Sometimes user does not know how to start. Demo videos are there for some but then the whole exercise would be irrelevant if we watch it beforehand.
A little bit explanation about the common errors we face. May be similar to Instruction sheet, some common error sheet should be there.
James is a very intelligent man and knows what he is saying. His explanations are good and relevant. He knows how to keep a boring session interesting especially that Legacy Code stuff.
I have started already. I want to put forward my knowledge ASAP. But it will take sometime to actually start i.e. getting an output.
Challenges to applying:
1. No Challenge as far as management is concerned, as I am encouraged to put TDD into my daily routine
2. The actual challenge is to put the frame work and then start it
The session was really good. It changed my prospective as how to make my life easier by doing my development in TDD way. I have miles to go but I have taken the first step.
Legacy code workshop:
Recommend to others: