Course code: ZOO-1
  • Years with company: 1
  • Years programming: 10
  • Primary programming language: C++
  • Other programming languages: Python, C#, C
  • Unit test harnesses: Google test, Catch
  • Something else: I like C++, especially the "modern" kind.
  • Test practice now: I write unit tests (after writing the code :( )
  • Target system: Linux servers
  • Dev tools: Bazel, gdb, valgrind
  • Build time: 1-5 minutes
  • Coding standard: It contains stylistic guidance and known C++ pitfalls. Lacks "design" guidelines.
  • Function too long: When it's longer than 50 lines.
  • Code reviews: There is not universally agreed "checklist", it's often hard to get consensus among reviewers about the "readable" coding style.
  • Code time: 6
  • Test time: 2
  • Debug time: 2
  • Favorite thing about dev: I like the design/creative process.
  • Least favorite thing about dev: Cryptic bugs that are hidden and hard to observe and root cause.
  • Tdd knowledge: It's an effective way of coding, have used it in the past, but not extensively.
  • Why are you attending: I'd like to revisit TDD + try spread the word within my team. I'd like to get better at maintaining + testing legacy code with less frustration.
  • Back