Course code: QCOM-4
  • Years with company: 1
  • Years programming: 11
  • Primary programming language: C++
  • Other programming languages: C, Java, VHDL/SystemVerilog, some scripting languages
  • Unit test harnesses: CUnit
  • Something else: I enjoy low level programming, the closer to the hardware the better.
  • Test practice now: 1st stage: compiles correctly 2nd stage: code review 3rd stage: blackbox testing on target device
  • Target system: Android / Linux
  • Dev tools: Eclipse, vi
  • Build time: 1-5 minutes
  • Coding standard: We follow the Qualcomm specific rules for secure coding.
  • Function too long: Rule of thumb: If it is longer than one screen page.
  • Code reviews: We use gerrit to review code of peers in the final stage of development, i.e. shortly before release.
  • Code time: 20
  • Test time: 30
  • Debug time: 50
  • Favorite thing about dev: I like the quick feedback when a new feature is finally working.
  • Least favorite thing about dev: Debugging unknown code written by the open source community with the "sparse" comment style.
  • Tdd knowledge: TDD is a coding style where tests are implemented first. During each step in development, all tests have to be passing. It gives direct feedback to the developer. Drawbacks are a false feeling of security due to weak test coverage.
  • Why are you attending: To have more arguments for a paradigm shift in my team towards earlier testing. To use test driven development in my own work.
  • Back