TDD for Embedded C
2018-04-27 15:30:18 UTC
Most useful learnings:
I really enjoyed the 3rd day agile training aspect. I liked learning how it could be used.
I liked the more advanced TDD courses on the 2nd day.
Concepts v exercises:
Presentation v discussion:
Too much presentation
I wasn't crazy about the pair programming, I felt like I wasn't able to focus or think through the concepts in that kind of environment.
I felt like we spent too much time talking about the initial TDD feedback. While I understand the reason for discussing the feedback early I felt like it didn't need to be as long as it was.
The 3rd day agile training I liked the best but it felt like there was too much content to cover in one day.
I thought James was very knowledgeable on the topics being discussed. He had the experience of being a developer which allowed him to easily be able to answer questions and provide feedback for why or why not something would be useful.
With TDD yes. With Agile, applying it an established waterfall process will take some time but the organization seems open to change and multiple people have been looking into it.
Challenges to applying:
With TDD, when it makes sense not to unit test. I know this sounds counter-initiative, but certain projects are blindly trying to achieve 100% coverage. While this sounds ideal, project team members are spending weeks creating units tests that aren't necessary. It was mentioned typically UI's aren't beneficial to do TDD, we talked about some other concepts too, but we will continue to struggle with this due to blind '100%' goal metrics.
Legacy code workshop:
Recommend to others: