Course code: WEB-32
  • Years with company: 14
  • Years programming: 17
  • Primary programming language: C++
  • Other programming languages: JavaScript, Bash
  • Unit test harnesses: GoogleTest, Catch2
  • Something else: Relatively new to team (8 months)
  • Test practice now: Full system-level tests; Developing unit tests
  • Target system: Ubuntu, Intel Core i5 dual core @ 2.60GHz, 8GB RAM
  • Dev tools: GCC, CMake, Visual Studio Code, Docker, Bitbucket, Jira, Jenkins, SonarQube
  • Build time: 31-60 seconds
  • Coding standard: Code is automatically scanned using several static code analyzers via Jenkins pipeline build, results checked against quality profile rules via SonarQube, all issues to be resolved by fixing code or updating rules
  • Function too long: It has more than one job or produces multiple outputs
  • Code reviews: Pull request for most changes, typically 1-2 reviewers within our dev team; Static code analysis via Jenkins pipeline for all automated builds, reports pushed to SonarQube for issue tracking and resolution
  • Code time: 40?
  • Test time: 30?
  • Debug time: 30?
  • Favorite thing about dev: Solving problems and delivering a high quality product that performs as good or better than expected
  • Least favorite thing about dev: Legacy and 3rd party code that hinders new features, maintenance, and product quality
  • Tdd knowledge: High-level concept
  • Why are you attending: To write better code and unit tests
  • Back