Course code: BARR-10
  • Years with company: 2
  • Years programming: 14
  • Primary programming language: C/C++
  • Other programming languages: Ruby, Julia, Matlab
  • Unit test harnesses: gmock
  • Something else: I was a competitive water skier in college.
  • Test practice now: Some automation w/ Cygwin and gmock, but mostly manual on-target testing though a debugger
  • Target system: 16-bit NXP MCU (S12Z)
  • Dev tools: CodeWarrior, Visual Studio Code, PE Micro debugger
  • Build time: 11-30 seconds
  • Coding standard: Internally developed, but references the JSF-AV rules, MISRA-C guidelines, and articles from Michael Barr and Dan Saks on embedded.com
  • Function too long: I have to scroll to read the whole thing
  • Code reviews: they are done virtually through our VCS (GitLab)
  • Code time: 40
  • Test time: 40
  • Debug time: 20
  • Favorite thing about dev: the artistic creation aspect of it, and the immediate effects you can have on the physical world with embedded systems
  • Least favorite thing about dev: explaining computational complexity, tell-don't-ask, and other software paradigms to non-software folks. Also the limitations of cross-compiling are annoying.
  • Tdd knowledge: I went through the first half of James's book and tried it out with our system at work.
  • Why are you attending: To make connections with other embedded developers and get more exposure to the use of agile methods in the embedded realm.
  • Back