TDD for Embedded C
2020-03-26 20:34:39 UTC
Most useful learnings:
Well I learn:
1)To write test for my code then let test drive my code.
2)Not to analysis suffer from analysis paralysis, let about the problem while you TDD you code.
3)Work in small incremental steps/Slice the problem.
4)Slow down do go fast. Why am I in a hurry to write bugs that's going to take me away from the things I love.
5)Because I am a jack-of-all-trades and don't code as often as I like, TDD is a must!
Concepts v exercises:
Presentation v discussion:
I don't know if everyone would enjoy it (I think you have done this before), but I it would be eye opening to assign the circular buffer exercise prior to the course. Then the students can see how different it turned out by doing TDD. Finally, as a bonus or on the last day, have the student test the "legacy" circular buffer and improve it.
For someone like me that do not code all of the time it would be helpful to introduce the exercise the day prior to when the exercise will be done on class and perhaps have a similar bonus exercise assigned as homework with the assigned video of the day.
I enjoyed you delivery, anecdotes, and jokes.
I will start tomorrow, but with home projects and hubby type of stuff. I currently have no FW work that I can do remotely.
Challenges to applying:
The challenge is that in my organization change happens, by design, organically. In other words, someone changed the way they did things and improved their process; then someone else notice the changed and finds it useful or better than the status-quo. So, change happen slowly. However, that why I attended the class I so the value of the method in a colleague’s work.
Remote delivery worked; I think that there is enough to cover to justify a fourth day. I understand that you are still finding your way, I just want to mention that some of the things that you had to fix were not as distracting as the short interruption to change it. I don't think you would have much complains if you have not fixed them. Now some where actually helpful. I think it would be useful for you (all though time consuming) to record a couple of remote classes watch them and see for you self what should and shouldn't change with your tooling.
Legacy code workshop:
Recommend to others: