Course code: BARR-5
  • Years with company: 6
  • Years programming: +15
  • Primary programming language: C
  • Other programming languages: Labview, Visual Basic, 8051 Assembly
  • Unit test harnesses: none
  • Something else: Primarily an EE but only one capable of programming at company. Previous employment involved complex VHDL system designs.
  • Test practice now: mostly manually, some assembly testing
  • Target system: custom built PCBs using Microchip dsPIC33 uCs, native code, no OS
  • Dev tools: Mplab X, some code analysis tool, Spreadsheet,
  • Build time: 11-30 seconds
  • Coding standard: Trying to learn from what I self educate myself on
  • Function too long: When it does too much, probably
  • Code reviews: it'd be nice.
  • Code time: 30
  • Test time: 20
  • Debug time: 10
  • Favorite thing about dev: Didn't have design time in above: 40% Making a system that does what it should and then some.
  • Least favorite thing about dev: Lack of knowledge and understanding of software development by rest of company
  • Tdd knowledge: Have seen references to it and it being a good method. But I do not have a grasp for what it really means, especially in an embedded, no OS, native code design.
  • Why are you attending: TDD is supposed to be good,want to be better at my job. To do things right and more reliable. If/when I leave company, who ever might replace me doesn't look at what I have done and say "<insert favorite colorful word here>"!
  • Back