Course code: WEB-34
  • Years with company: 15
  • Years programming: 11
  • Primary programming language: c
  • Other programming languages: c#
  • Unit test harnesses: Not used any off-the-shelf harnesses. I have some custom test code for unit test
  • Something else: Started my career as a hardware engineer designing lock control circuit boards. I transitioned into firmware role 10 years ago developing c code for access control logic.
  • Test practice now: Custom unit test and functional testing are my primary test methods. I also occasionally use UART prints to log things for longer tests.
  • Target system: ARM processors
  • Dev tools: code composer by TI, CubeID by ST, Eclipse
  • Build time: Under 10 seconds
  • Coding standard: Modular coding with separated hardware layer and application layer files to promote portability.
  • Function too long: my rule of thumb is not more than 25lines of code in one function
  • Code reviews: 2 to 3 engineers participate in reviews. For changes we use beyond compare to identify modified code sections and those are reviewed in a meeting with peers.
  • Code time: 60
  • Test time: 30
  • Debug time: 10
  • Favorite thing about dev: The process of solving complex problems
  • Least favorite thing about dev: bugs that get past QA and end up in the field
  • Tdd knowledge: Not much
  • Why are you attending: Improve automated testing skills and hopefully learn about of-the-shelf testing tools available for c developers
  • Back