Course code: BARR-6
  • Years with company: 1
  • Years programming: 12+
  • Primary programming language: C
  • Other programming languages: C++, Python, Matlab, LabView, C#, Ruby, Java, Assembly
  • Unit test harnesses: CppUTest, Unity, NUnit, JUnit
  • Something else: Connecting ideas from disparate sources is awesome.
  • Test practice now: Large system tests done by a technician
  • Target system: A variety of safety products, legacy is mainly pic processors, future is hopefully ARM
  • Dev tools: Whatever is available
  • Build time: 31-60 seconds
  • Coding standard: Currently Minimal
  • Function too long: When you can't easily grasp what it's supposed to do or it no longer says what it does on the tin.
  • Code reviews: I have not had a code review at this company.
  • Code time: 5%
  • Test time: 25%
  • Debug time: 25%
  • Favorite thing about dev: Elegant solutions to problems, learning better ways of thinking about and doing things.
  • Least favorite thing about dev: Layers of useless process, information duplication, shoehorning.
  • Tdd knowledge: It works. It cuts development time, it improves code readability and functionality, and if done right, the tests can be treated as documentation of intent that grows with the code. It can move engineering a long way towards 'single source of truth'.
  • Why are you attending: I want to understand TDD for embedded systems well enough that I can train and convince other engineers on my team the value of developing this way.
  • Back