Course code: BARR-13
  • Years with company: 26
  • Years programming: 20
  • Primary programming language: ANSI C
  • Other programming languages: Assembly, C#, Visual Basic
  • Unit test harnesses: VectorCAST
  • Something else: I work for MSA.
  • Test practice now: VectorCAST for unit testing. Blackbox testing. White box testing. Independent verification testing.
  • Target system: My target system is typically ARM-Cortex-M cores right now for SIL3 certified gas detectors.
  • Dev tools: IAR Compilers, Bamboo build servers. VectorCAST unit test tools. SONARCube rules checkers.
  • Build time: 1-5 minutes
  • Coding standard: MSA coding standard we created ourselves.
  • Function too long: We try to achieve a complexity level of 10 or less for functions. This is not strictly enforced. I struggle with the limit of complexity of 10 vs. having multiple small functions and increasing the stack complexity of a design.
  • Code reviews: Right now code reviews are performed as pull requests using the GIT flow.
  • Code time: 40
  • Test time: 40
  • Debug time: 20
  • Favorite thing about dev: I like engineering a product and providing a robust design to production.
  • Least favorite thing about dev: I do not like that management thinks changing software is just a matter of a few key strokes and makes oversimplifies the change and verification processes that are required. Management changes tools we use thinking the tools are the issue.
  • Tdd knowledge: From what I understand this is when you write our unit tests first and then you write your code second in the process flow.
  • Why are you attending: I was asked to attend. I am looking for some ideas of how to make some improvements for my development work.
  • Back