TDD for Embedded C
2021-01-15 03:27:41 UTC
Most useful learnings:
Coming in to the course, I have already practiced a little bit of TDD. Although most of the tests I have done is mid-level, hardware-in-the-loop tests. I needed more training on unit tests, especially in embedded systems. I really liked learning about mocks and actually having a chance to work hands on with a working framework. It is quite different hearing about it from videos, and actually doing it.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
Too much presentation
I think extending the course from 3 half days to 5 days would be better to have more time for exercises.
I'm not sure how capable the editor is. It would be nice to go over a few of the more common shortcuts that the editor has, such as commenting out a block of code, or search and replace text. Someone else figured out how to do a revert, which I haven't. Also it took me awhile to figure out how to get back to the test output after navigating to the source code. For awhile, I kept re-running the test so I can see the test output again.
I liked how James was able to give feedback to the students during the exercises. I was amazed at how he was able to recall and show the actual steps wherein some students struggled a bit to the group. James does tend to keep talking without pause. I found it hard at times to ask questions during the lecture. Some of that is on me though, as I'm a bit shy and hesitant to disrupt.
Maybe. Our team is transitioning from C to RUST. We are still learning about the new language, and the tools associated with it.
Challenges to applying:
Having to learn a lot of new things at the same time.
I like the remote learning. I think it is just as effective as being in person.
Legacy code workshop:
Recommend to others: