Course code: BARR-6
  • Years with company: 2.5
  • Years programming: 40
  • Primary programming language: C++
  • Other programming languages: C
  • Unit test harnesses: Do not remember names
  • Something else: Former national champion fencer in my age group.
  • Test practice now: Visual Studio and/or GDB.
  • Target system: 32-bit Linux, usually an ancient version of Ubuntu; sometimes Windows
  • Dev tools: Visual Studio w/helpful plugins; emacs/GCC/GDB
  • Build time: 1-5 minutes
  • Coding standard: Rigorous C standard for licensing kits. Just helped write version 1 of our C++ standard.
  • Function too long: When I want to chop it up into subroutines.
  • Code reviews: I do wish I could get more of my colleagues to review my code!
  • Code time: 15
  • Test time: 7
  • Debug time: 8
  • Favorite thing about dev: I'm very good at it. It is very like creating something out of nothing -- making organized behavior out of chaos. I like creating useful tools for people to use to improve their lives.
  • Least favorite thing about dev: There is rarely time to write good code for a product. There is too much pressure to get something out the door *now*, irrespective of whether it can be maintained or extended in the future.
  • Tdd knowledge: Write a test -- it will fail. Write code for the feature that is being testing, get the test working. Repeat as needed.
  • Why are you attending: Unit test have have been useful for me in the past; unit testing is very often neglected because "there's no time." I want to learn better techniques for incorporating unit tests and developing the discipline to add them habitually.
  • Back