Course code: BARR-12
  • Years with company: 1
  • Years programming: 13
  • Primary programming language: C/C++
  • Other programming languages: Python, Bash. I have used Scheme in the past
  • Unit test harnesses: cpputest, google test
  • Something else: I enjoy skiing
  • Test practice now: Some unit tests, mostly system/QA testing
  • Target system: ARM based MCU
  • Dev tools: IAR, Cygwin, SVN, Git
  • Build time: 1-5 minutes
  • Coding standard: Written on a wiki, added to as needed
  • Function too long: Usually if it doesn't fit on the screen. I also look for depth of if statements and loops, and any redundancy between multiple if statements.
  • Code reviews: After each ~2 week sprint we have 2 days of Code Review and test. Any meaningful changes should (and for the most part are) sent out to two other people, and one tester (who may also be one of the two reviewers).
  • Code time: 70
  • Test time: 10
  • Debug time: 20
  • Favorite thing about dev: The creativity required in writing "good code." I enjoy the challenge of finding solutions that are simple and elegant.
  • Least favorite thing about dev: The tools (especially for embedded).
  • Tdd knowledge: I have read Test-Driven Development for Embedded C
  • Why are you attending: I have read your book, and my manager is interested in improving our software processes.
  • Back