Course code: BARR-6
  • Years with company: 3
  • Years programming: 5
  • Primary programming language: Python
  • Other programming languages: C, Go, Javascript
  • Unit test harnesses: Google Test
  • Something else: I'm a musician and so are a lot of the people coming from Dolby.
  • Test practice now: I unit test in Python using the unittest module. I've experimented with pytest. For C, I use Google Test and call my C code from C++.
  • Target system: x86 Windows is the most important, but we also support Mac and Linux. TI DSPs are an important target as well.
  • Dev tools: Visual Studio, Xcode, Code Composer
  • Build time: 30-60 minutes
  • Coding standard: We having coding guidelines that are used company wide. They are not strictly enforced.
  • Function too long: If you run out of stack space. Just kidding. Always try to find a balance between brevity and intelligibility. A hard limit isn't necessary and if you make 80 one-line functions it may be more difficult than reading one 80 line function.
  • Code reviews: Code reviews are done using Swarm. 3-4 people are involved.
  • Code time: 30
  • Test time: 50
  • Debug time: 20
  • Favorite thing about dev: Breaking down complicated problems into more manageable systems. The instant gratification of firing up something you created something and can seeing it working autonomously. It's easier than physical labor.
  • Least favorite thing about dev: Hard to comprehend bugs that make you feel like you're going insane. The boring work in between writing code.
  • Tdd knowledge: Only the process of red, green, refactor.
  • Why are you attending: We don't test enough at our company and we have a lot of legacy code. We hope to find a way to deal with how we can introduce tests to that legacy code and hopefully move to TDD in the future
  • Back