Course code: SAND-1
  • Years with company: 8
  • Years programming: 40
  • Primary programming language: C++
  • Other programming languages: C, Matlab, C#, F#
  • Unit test harnesses: I write what I need.
  • Something else: I started out doing embedded code in C and assembler. I do lots of analysis code in Matlab and desktop apps in C#. I'm now getting back into doing embedded code.
  • Test practice now: Most important is to design code as separate testable modules. I can then write a test program that pumps data through the modules and checks the outputs.
  • Target system: ARM processor, battery powered, lots of sensors, radio communications.
  • Dev tools: IAR (maybe Green Hills also)
  • Build time: 1-5 minutes
  • Coding standard: I strive for correctness, test-ability, and readability. I try to use best practices for each language.
  • Function too long: When there is excessive scrolling to figure out what it's doing. It's not necessarily dependent on the number of lines.
  • Code reviews: Project dependent. Some have none. Others have full up reviews in TeamForge + Gerrit.
  • Code time: 70w/design
  • Test time: 20
  • Debug time: 10
  • Favorite thing about dev: It's both creative and logical. It produces tools that increase our productivity and quality of our work.
  • Least favorite thing about dev: I work in science and engineering software, so I don't have anything to complain about. If I had to work on web sites, then that would be another story.
  • Tdd knowledge: Tests are written first, then code modules to pass the tests.
  • Why are you attending: Our group is trying to do things better.
  • Back