TDD for C++
2021-04-15 10:39:16 UTC
Most useful learnings:
changing how my brain approches a problem
dividing a problem into small steps (it's a huge change !)
coding tests can be interesting and fun and does not take that much time (in an environment that enables tests to be done)
Concepts v exercises:
Presentation v discussion:
it's a bit difficult to attend the full course AND practice homeworks while keeping half a day of workload.
Maybe tell companies that they need to free attendees for the whole day, so they can focus on subjects
maybe with a concrete case where 3 classes have to be tested independantly, but also together ?
One difficulty is to work on the exercise while the instructor talks with other attendees. It could be interesting to have a special zoom room acting as an "instructor desk" where people could queue and get their help/answer from instructor each after another. That way, people don't get distracted. And if the instructor wants to say something for everyone he can just go back to the main room and tell his thing.
James was a great instructor, I personally understood him well, and he was able to rollback to unanswered questions or misunderstandings. I appreciated the exercises provided (though it was a bit too low level/hardware related)
Hopefully we can use it in our refactoring process. I would say I can start based on some example you have provided.
Challenges to applying:
main challenge is the time given by our managers for that. They need to understand the whole test subject has been put aside for many years, and if we now want to make things reusable, we have to spend time on it now and can't reach our objectives without them.
Technically, I think this can be applied on our product and it will me even more useful to people dedicated to providing new features.
I look forward to the workshop this afternoon to see a concrete example on our codebase.
Legacy code workshop:
Recommend to others: