Course code: SP-005
  • Years with company: 0
  • Years programming: 13
  • Primary programming language: C
  • Other programming languages: Python, C++, make
  • Unit test harnesses: pytest
  • Something else: I spent 15 years in the military and 5 of them as an Assistant Professor at West Point, which I absolutely loved. I'll probably be a teacher the rest of my life.
  • Test practice now: Not really at all, for simple projects. Maybe write tests at the end for validation testing. For a security-focused project I'm working on, identify a feature or defense I want to add then write the test to see it fail, fix it, then watch it pass.
  • Target system: Mostly ARM Cortex-M devices. Some smaller 8- and 16-bit MCUs like PICs, MSP430s, or AVRs.
  • Dev tools: Sublime Text, STM32CubeIDE, scons, make, OpenOCD, MPLAB X IDE, Arduino IDE
  • Build time: 1-5 minutes
  • Coding standard: I've read the Barr Group coding standard, so I probably try to follow that as best I can
  • Function too long: When I can't think through what its supposed to do, what the edge cases are
  • Code reviews: Single-member LLC, so there aren't any, really
  • Code time: 40
  • Test time: 30
  • Debug time: 30
  • Favorite thing about dev: It's such a fun puzzle! With basically nothing you can't do.
  • Least favorite thing about dev: Brittle code/build toolchains/etc. Little annoying details that make it hard to do simple things.
  • Tdd knowledge: Lots! Though I'm not a daily practitioner. I've read James' book two or three times, though.
  • Why are you attending: James gave me a free seat :) I'm excited to have formal TDD training and maybe become an instructor!