Course code: BARR-13
  • Years with company: 2
  • Years programming: 25
  • Primary programming language: C/C++
  • Other programming languages: Python somewhat regularly
  • Unit test harnesses: CppUtest, Google Mock/Test
  • Something else: I like biking, swimming, 3D printing and mechanical modeling, astronomy, violin, music, ... lots of hobbies!
  • Test practice now: Every build during development, my unit tests are run immediately on boot.
  • Target system: It is a Kinetis-powered system running FreeRTOS doing automotive communications with a wide variety of protocols.
  • Dev tools: Sublime Text, IAR Embedded Workbench, AutoIt, Visual Studio 2017, and more.
  • Build time: Under 10 seconds
  • Coding standard: Refactor for reuse and maintainability.
  • Function too long: In a nutshell, if the name of the function doesn't easily describe what the function does, it likely does way too much.
  • Code reviews: Currently no formal code review process where I work, but I have been heavily involved in the code review process at a previous company using Atlassian Crucible.
  • Code time: 40
  • Test time: 40
  • Debug time: 20
  • Favorite thing about dev: The feeling of satisfaction solving problems.
  • Least favorite thing about dev: When the development tools don't work consistently or are slow!
  • Tdd knowledge: I've read Modern TDD in C++ a few times and used it actively in the development of the firmware for which I'm directly responsible.
  • Why are you attending: I know there's a ton to learn with mocking things up in embedded land and there's nothing like reviewing a concept outside your normal environment to improve your understanding and depth of knowledge.
  • Back