TDD for Embedded C
2018-09-06 18:05:02 UTC
Most useful learnings:
TDD development cycle (small steps). Retraining my flow took effort, and having multiple exercises with feedback allowed me to effectively adapt that process. Practical example with mocking (and the fact that I want to avoid it) were great.
Concepts v exercises:
Presentation v discussion:
I could use a few more short breaks (2-5min) to get up, stretch, and get water. I prefer this to a 15 minute break.
A link-time substitution example, or other mocking examples, would be helpful. We discussed the problem but actually being required to perform the processes make it more concrete.
I really enjoy hearing war stories. I appreciated receiving feedback while performing the exercises - it helped me retrain my behavior. Questions via chat didn't seem to work so well due to time delay between your comments and when the questions were noticed. Not sure of a better way to handle that aspect.
Bring it on!
Yes - last night I set up my current project for TDD and have my IDE configured to compile + run tests with a keystroke.
Challenges to applying:
If there is a challenge, it will be in simply building the habit. I am the master of my own company :)
I was quite impressed with the effectiveness of the remote workshop. I think that the number of programming exercises really helped the workshop. Certainly this format would not have worked for something like software architecture, where there is more discussion and white-boarding. I would recommend the remote version to other developers.
Getting up at 5am every day was hard... but I also enjoy that I can still run my business while taking the workshop, so no real complaints.
Legacy code workshop:
Recommend to others: