Course code: ZOO-1
  • Years with company: 3.5
  • Years programming: 20
  • Primary programming language: C++
  • Other programming languages: python, bourne shell, rust
  • Unit test harnesses: Gtest, unittest
  • Something else: I have code running inside of people
  • Test practice now: gtest
  • Target system: beefy x64
  • Dev tools: vim, gdb, bazel, valgrind, asan, tsan
  • Build time: 1-5 minutes
  • Coding standard: we use a derivative of the google style guide. I try to enforce additional C++11 feature usage, such as final, unique_ptr, etc.
  • Function too long: When more than one question is answered.
  • Code reviews: each file must be marked as reviewed by any reviewer. Typical questions are more about style than design and usually a lack of tests is considered to be OK.
  • Code time: 30
  • Test time: 20
  • Debug time: 50
  • Favorite thing about dev: interface design and seeing an evolution of clean interconnections
  • Least favorite thing about dev: debugging hard-to-reach code
  • Tdd knowledge: Use tests to describe your requirements at whatever level you're aware of them. Whenever a new requirement is uncovered, new tests should follow. Don't write code unless it already has tests describing its requirements.
  • Why are you attending: I want to become a better, more effective developer.
  • Back