TDD for Embedded C
2020-03-12 18:06:51 UTC
Most useful learnings:
Concept of breaking complex functions into smaller testable parts and how useful that can be
Concepts v exercises:
Presentation v discussion:
It might have been useful to have a "worked out" file made available for exercises. If it's better to delay availability 'til - say - halfway through the allotted time, then that's okay. My point: the concepts are really great but it takes time and deeper understanding to implement against concepts. It's sometimes tough to assimilate the concepts and be a "slick coder" at the same time. Having "worked out" examples readily available would have been helpful.
As above, more worked out answer sets. Also, perhaps a quick class setup example showing "...on this tab, keep the diagrams for what you're working on, on this page the worked out answers, and on this tab the work area....you the student may want to go back & forth a bunch and we've got a limited amt of time". Something like that
James is a funny guy who's got a very practical idea about what it is to do embedded programming.
Yes, but the caveat is that one starts small and works it in. We've got a big organization that's very process driven and big disruptions are not accepted easily.
Challenges to applying:
Rigid process backed by people in authority
Remote delivery is fine. I don't really know how it could have been better in person. Maybe doing the lab work in groups if we were there. For a classroom setting, it's tough to replicate the personal contact that's so productive with in-person/in-
Legacy code workshop:
Recommend to others: