Course code: BARR-4
  • Years with company: 24
  • Years programming: 38
  • Primary programming language: C
  • Other programming languages: Visual Basic for Applications
  • Unit test harnesses: none
  • Something else: Developing our company's software development process to yield "better code, faster" (Jack Ganssle). Hardware and software development from small 8bit and 16 bit processors and now ARM Kinestis processors for controls applications that require UL-60730 certification.
  • Test practice now: Black box test procedures on engineering test fixtures and final project.
  • Target system: Water heaters with controls 64K code range.
  • Dev tools: CodeWarrior and KDS
  • Build time: 31-60 seconds
  • Coding standard: We developed internal standard for C using object oriented-like methodolgy with formatting standards. These comply mostly with other standards I have read like Netruino.
  • Function too long: When printed it goes over more that about 3 pages at approximately size 12 font of Courier new
  • Code reviews: For many years they were scarce and done in one giant effort at the end of the project. We just started using them this past year using CodeReviewer to review changes to code and will be starting new projects using it on an ongoing basis.
  • Code time: 30
  • Test time: 20
  • Debug time: 50
  • Favorite thing about dev: Creative aspect of problem solving, architecting the code.
  • Least favorite thing about dev: Debug and test. Fixing problems after they get to the field.
  • Tdd knowledge: It tests the code at the module (white box level) thoroughly and frequently.
  • Why are you attending: I want to introduce Test Driven Development into our software processes to improve the quality of my code and decrease the time debugging and testing.
  • Back