TDD for Embedded C
2017-09-29 21:06:03 UTC
Most useful learnings:
How to structure tests and use the tools.
How to handle legacy code bases.
Argh my brain hurts from holding too much.
Concepts v exercises:
Presentation v discussion:
It was hard to follow along on the one screen which was somewhat dark.
Might be useful to have a split screen and/or have the students provide the answers on what to do next so the follow along work is more interactive and easier to follow.
Everyone struggled at first. Sometimes it felt like it was not clear what to do next.
Without having James/teacher nearby it is easy to get discouraged.
Would be helpful to get a list of hints if we are stuck and working solo.
Good examples and engaging.
Willing to help at all levels.
It's a Saturday and team needs to rest.
However, I do have an idea of what steps to proceed on the stinky areas of code.
Challenges to applying:
Getting people to take a step back and consider doing it differently.
The hectic pace makes it hard but some of my team have done this before and are more amendable.
Legacy code workshop:
Recommend to others: