Course code: BAX-1
  • Years with company: 1.5 years
  • Years programming: 14
  • Primary programming language: C++
  • Other programming languages: C#
  • Unit test harnesses: VectorCAST
  • Something else: I have been in the medical device software arena for over 13 years, so I have a good grasp on software in a safety critical, regulated environment.
  • Test practice now: Manually test in target system based on requirements or design expectations Write a test harness "hello world" to execute code I pulled out of a system
  • Target system: An NXP iMX6 Dual Core processor running at 800 MHz running an Integrity operating system
  • Dev tools: Visual Studio, Understand, Green Hills MULTI, Cygwin
  • Build time: 1-5 minutes
  • Coding standard: We have a formalized coding standard. I am not sure it is used during development or enforced during code reviews.
  • Function too long: A given function should have strong functional cohesion, the name should describe what it does. If these things hold then the function can grow. In general, one two pages is a good length. It depends more strongly on purpose than lines of code.
  • Code reviews: Some teams perform code reviews on a story by story basis to remove defects early. This is not required by our process. Formal code reviews happen to groups of code changes associated with feature changes that can span weeks to months.
  • Code time: 65
  • Test time: 25
  • Debug time: 10
  • Favorite thing about dev: Thinking critically about how systems will interact and ensuring a solid design before jumping into the code. It is a joy to write documentation that actually helps myself and others understand a system and maintain its architectural integrity.
  • Least favorite thing about dev: Producing documentation to check off that it was produced. Much of what external standards and the FDA require us to produce, if done correctly, will help us write better, more maintainable, software. This is rarely done well or valued.
  • Tdd knowledge: I went to a developers group meeting that covered TDD in C#. I have read Code Complete at least 6 times over the past 14 years. I attempt to write test cases against my requirements, design, and code that I will execute when I think I am done.
  • Why are you attending: I would like to encourage more diligent developer testing at my company and feel I can support that by being part of this training.
  • Back