Course code: JHAP-1
  • Years with company: 6
  • Years programming: 18
  • Primary programming language: C
  • Other programming languages: Python, Matlab, LabView, C++, Java, & Other domain specific.
  • Unit test harnesses: Primarily self-built unit test code.
  • Something else: Enjoy the mix of electrical and software skills used in embedded software development.
  • Test practice now: Feature specific unit testing during development. Hardware in the loop testing suite for system software as a whole.
  • Target system: Primarily ARM Cortex-Mx platforms.
  • Dev tools: IAR, GCC, Atmel Studio, & Simplicity Studio.
  • Build time: 11-30 seconds
  • Coding standard: Internally developed standards based on "Netrino Embedded C Coding Standard"
  • Function too long: Hard to follow or implements logic for multiple features or multiple parts of a complex feature.
  • Code reviews: Reviews with relevant team members for feature branches before merging with development branch.
  • Code time: 30%
  • Test time: 30%
  • Debug time: 40%
  • Favorite thing about dev: Finding clean and elegant solutions to problems. Getting to the bottom of troubleshooting exercises. Seeing things you developed doing what they were designed to do.
  • Least favorite thing about dev: Working with legacy code that was not written efficiently or flexibly enough for it's applied use. Dealing with bugs while working against deadlines when they should have been identified earlier in the process.
  • Tdd knowledge: Developing software with testablility at its core. Incorporating a framework for testing early on and not as an afterthought.
  • Why are you attending: I would like to expand my toolbox for embedded software testing and learn the skills to more easily integrate TDD into my projects. I also want to learn to efficiently reduce the number and scope of tests requiring hardware-in-the-loop testing.
  • Back