Course code: BARR-13
  • Years with company: 2
  • Years programming: 35
  • Primary programming language: C
  • Other programming languages: Python
  • Unit test harnesses: CppUTest, home brew
  • Something else: Outdoor enthusiast.
  • Test practice now: Some debug stepping confirmation and final testing in the target environment.
  • Target system: ARM Cortex M3/M4 mix
  • Dev tools: IAR, Ozone, gcc
  • Build time: 1-5 minutes
  • Coding standard: Currently very limited. Targeting adoption of a slightly modified BARR-C:2018.
  • Function too long: When it does more than its core purpose and/or gets complex or too long (> ~200 verbose lines).
  • Code reviews: Informal BitBucket reviews requiring two approvals from a potentially large audience.
  • Code time: 20
  • Test time: 40
  • Debug time: 40
  • Favorite thing about dev: Building solutions to problems.
  • Least favorite thing about dev: Dealing with messy code and lacking documentation.
  • Tdd knowledge: That it focuses on establishing tests first to provide a pathway and automated checks that validate the functionality of developed code.
  • Why are you attending: Personal interest combined with company initiative to change to this method.
  • Back