• Course: TDD for Embedded C++
  • Date entered: 2018-06-11 15:39:27 UTC
  • Course rating: Excellent
  • Most useful learnings: I left with this takeaway: I need to understand why my code works, and I can prove that through carefully testing, coding, and compiling one piece at a time.
  • Concepts v exercises: Good balance
  • Presentation v discussion: Good balance
  • Course improvements: More discussion and exercises on using mocks, I felt I did not understand everything there.
  • Exercise rating: Very Good
  • Exercise improvements:
  • Instructor comments: Easy to listen to and I appreciate his willingness to demonstrate in front of the class how easy it is to make mistakes. It's easy for any programmers to let pride get in the way and the instructor brought the right attitude to demonstrate the need for a disciplined approach of TDD.
  • Better prepared: Bring it on!
  • Start tomorrow: No, finishing up some manual testing, then I will start working on this
  • Challenges to applying: I think our software organization has software developers operating in silos. A specific example is our developers feel like it's our dev ops responsibility to get the ball rolling on getting a version of google test, get it under configuration management, and have everything ready to start using it. Since we have the direction from our manager to do this, I think our software developers need to figure out how to work together to solve the issues we will face to get our code under test and how to organize all this work.
  • Other comments:
  • Legacy code workshop: Yes
  • Recommend to others: No
  • Quote permission: Yes