Course code: CISCO-14
  • Years with company: 12
  • Years programming: 30+
  • Primary programming language: C++
  • Other programming languages: C,python,SQL
  • Unit test harnesses: Homegrown
  • Something else: I have three adult children.
  • Test practice now: Manually, once; then as-needed.
  • Target system: IP video set top boxes with various different hardware, SOCs, kernels, etc.
  • Dev tools: gcc, make, atom, vim
  • Build time: Under 10 seconds
  • Coding standard: Ad hoc, loosely defined.
  • Function too long: Takes more than a screen (or half a screen on my vertical monitor)
  • Code reviews: All code is reviewed before merging to the tip via Gerrit; Jenkins performs build testing.
  • Code time: 80
  • Test time: 10
  • Debug time: 10
  • Favorite thing about dev: Solving puzzles, creating clean APIs, creating clean and concise code.
  • Least favorite thing about dev: Mysterious bugs; hardware anomalies.
  • Tdd knowledge: I've studied a bit, but nothing formal. I'm not sure want to be a TDD convert, but I would like to have a formal testing framework in place. I've designed some for embedded systems, but we have not moved to automating it for test hardware.
  • Why are you attending: To get the right mindset and authority to bring a test-driven mentality to my team.
  • Back