Course:
TDD for Embedded C++
Date entered:
2019-01-17 22:16:15 UTC
Course rating:
Very Good
Most useful learnings:
Learning about mocks, spies, and fakes. I'd already been writing simpler unit tests for my python code if it didn't require system dependencies like socket or USB interfaces, but I think I'm better equipped now to tackle learning equivalent mocking tools of python unit test framework, in addition to using this for our c and c++ code.
Concepts v exercises:
Good balance
Presentation v discussion:
Good balance
Course improvements:
The lack of syntax highlighting in the exercise platform was at times annoying. I don't know if other similar platforms would be better about providing it, but for someone who's grown up after at least basic syntax highlighting was ubiquitous in most programing oriented text editors, it helps catch a lot of little things before you even get to the compiler like missing {} or un-closed "", etc.
Exercise rating:
Very Good
Exercise improvements:
Other than my complaint about the platform tool used not having syntax highlighting, I thought the exercises were pretty good. I struggled a little early on with the second one, mostly out of relative lack of familiarity with the intricacies of c++ vs c.
Instructor comments:
I though James did a good job teaching the course. He was clear about laying out his philosophy about why TDD was a good idea, and gave good feedback to us in the exercises about how to both better our work flow to align with TDD, and comments about what we could do better in our code structure itself.
Better prepared:
Much better
Start tomorrow:
Sort of.
Much of the code base I work on is legacy, and it is often quite time consuming to disentangle stuff enough to write tests, but on new products, internal tools, etc, I should be able to apply the lessons soon.
Challenges to applying:
Much of the code base I work on is legacy code that wasn't written with test-ability in mind.
Other comments:
I didn't find remote delivery to be much of an issue outside of tuning out local office noise which is not a reflection on the delivery, but rather the lack of separate space being made available by my company as I was the only developer signed up for this session.
Legacy code workshop:
No
Recommend to others:
Yes
Quote permission:
Yes