TDD for Embedded C
2018-08-30 18:09:02 UTC
Most useful learnings:
It's illogical to go down the route of "Tests waste time, I'm testing stupid shit." We cannot anticipate what bugs we will write, that would be impossible and make us very un-human.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
Require further exposition when multi-disciplinary groups get together to mob code. It would be awkward but helpful to require a quick hot-seat presentation on a whiteboard about the overall system description.
Further clarity with the open-ended one.
Please stay up to date with diversity and inclusion training, otherwise you are fabulous and overall are an approachable dude.
Yes. I intend to look over my recent commits and open tickets and see how I was violating these principles, and attempt to apply fixes.
Challenges to applying:
Unusual constraints (safety, psssh) full-spectrum development with overlap.
Careful about announcing the number of women in the room... You missed one. Also some people don't want to be called 'young lady'
Legacy code workshop:
Recommend to others: