TDD for Embedded C
2016-06-09 16:51:54 UTC
Most useful learnings:
Mocking C functions
Concepts v exercises:
Presentation v discussion:
Too much presentation
Shorter blocks of presentation/talk/code. It allows for shorter feedback loops and improves engagement.
cyber-dojo is not my favorite development environment, but I don't have obvious better solutions. The closest I can come up with is distributing virtual box images for a linux station set up with development tools. But that doesn't get us the ability to view shared code. Possibly add a disk monitor that looks for new file updates and pushes them to a common source control repository. This seems overly complicated and error prone.
I won't get to work on an embedded project tomorrow. But I will be able to apply it to upcoming personal projects.
Challenges to applying:
My workplace is an agile consultancy, so we're fully on board with test driven development. We are only taking baby steps in the embedded world though.
I had a lot of trouble remaining engaged during the long blocks of presentation. Please keep in mind that human attention span is limited to five or ten minutes tops, and ten is really pushing it. Switching to a new or related thing frequently is good.
Legacy code workshop:
Recommend to others: