TDD for Embedded C
2020-02-13 22:45:30 UTC
Most useful learnings:
TDD! :) It's also very helpful to hear others actually saying that modularization is worthwhile.
Concepts v exercises:
Presentation v discussion:
There might have been more clues as to exactly what you were looking for with a given test. In our case, we were able to come up with the testing that was desired, but that's probably because we have over 35-45 combined years experience (and all in embedded systems). Maybe go back to your recordings and get some of the things you told the less experienced people to help them along and add them to the notes/instructions.
James is a good instructor in that he definitely knows his topic. I never felt like any topic came up either with his presentation or things added by the attendees that he didn't immediately know an answer. I would like to have all of his examples rewritten using a published coding standard and not just his internally known one. This removes ambiguity and make things easier to read, etc. Perhaps using Barr and associates.
Bring it on!
I can start today; however, we need to agree on which platform we'd like to use here. This is because whatever we (the three attendees) agree on will be what we impose on the rest of our colleagues. I want to be able to get them as excited about TDD as I have become.
Challenges to applying:
Lots of legacy code. James went over this a little bit, but there was no example/workshop on this.
I really like the use of Cyber Dojo as a development environment. The slight annoyances (not being able to right click a function and go to its definition) were overshadowed by the benefits (being able to see everyone's code/progress, etc. We took the colors and number of commits as a challenge against the others :)
Legacy code workshop:
Recommend to others: