Course code: VIAVI-1
  • Years with company: 1
  • Years programming: 6
  • Primary programming language: c++
  • Other programming languages: python, perl, Javascript
  • Unit test harnesses: Jasmine, some google test
  • Something else: 2014 Penn State grad.
  • Test practice now: edit, build, check feature manually on hardware. Want to do TDD, but haven't bit the bullet to pay the up front cost of learning how to do it in our system.
  • Target system: .
  • Dev tools: I primarily work in the terminal. vim, tmux.
  • Build time: 1-5 minutes
  • Coding standard: A consistent level of abstraction within a function and good naming are very important to me.
  • Function too long: When it takes longer than a minute to understand what it does. Also if it is difficult to come up with a name for it.
  • Code reviews: Effective when used. Some of the veteran developers don't participate.
  • Code time: 50
  • Test time: 20
  • Debug time: 30
  • Favorite thing about dev: Solving problems. Seeing a feature through to completion.
  • Least favorite thing about dev: Getting bogged down trying to fix bugs.
  • Tdd knowledge: Steps of TDD: Find need for a new function. Write tests for said function. Tests fail because function doesn't exist yet. Write function; tests pass. I've read a lot about how it works and how great it is, but I haven't done any unfortunately.
  • Why are you attending: I want to learn how to use TDD well enough so that I can help get more people using it. Our testing practices are dated, and the only way to get up to date is to educate people on good testing practices.
  • Back