Course code: BLUE-1
  • Years with company: 1.5
  • Years programming: 10
  • Primary programming language: C/C++
  • Other programming languages: Python
  • Unit test harnesses: Googletest
  • Something else: I work on/with a large variety of software packages. Some are impenetrable monoliths and some are small, well-tested libraries. Most of the code is something I am a victim of rather than something I designed.
  • Test practice now: Various levels of test ranging from code developed with TDD all the way to "give this to my (internal) customer and hope it still works because there is no other way to tell"
  • Target system: Combination of real time and not real time software on x86-based servers
  • Dev tools: clang or gcc, cmake, google test, vim
  • Build time: Under 10 seconds
  • Coding standard: My personal standard is that if it is not tested it is broken
  • Function too long: It does not do one thing
  • Code reviews: I hope people are paying attention
  • Code time: 40
  • Test time: 55
  • Debug time: 5
  • Favorite thing about dev: Fairly regular doses of instant gratification. Easy to improve software to adapt to changing needs (as opposed to hardware, which is hard).
  • Least favorite thing about dev: Having to deal with pathologically bad products that I cannot change.
  • Tdd knowledge: TDD changed my life
  • Why are you attending: I already practice TDD for all my new code and as much as I can on new code I write in systems that I do not have design authority to fundamentally change. I am hoping to learn new TDD techniques and hone the ones I have.
  • Back