Course code: WEB-22
  • Years with company: 5
  • Years programming: 6
  • Primary programming language: C++
  • Other programming languages: C
  • Unit test harnesses: Not sure? Keil ULink Pro debug tool?
  • Something else: I like coding and music
  • Test practice now: We have a test actor that can work as the sending and receiving end of each code execution. This can be scaled from single events to full features. We leave #ifdef-ed in case we ever need to reverify code that we make changes to.
  • Target system: Embedded Atmel microprocessor
  • Dev tools: Keil IDE with the Keil ULink Pro
  • Build time: Under 10 seconds
  • Coding standard: Tried to stick closely to the BARR Group Embedded C coding standard
  • Function too long: Generally when it takes up more than the screen.
  • Code reviews: Our initial code drafts were brought in without much review because of time constraints, we're working on cleaning up now. Anytime we merged new code we used BeyondCompare to see exactly which code has changed.
  • Code time: 65%
  • Test time: 15%
  • Debug time: 20%
  • Favorite thing about dev: If it breaks or doesn't work I can fix it
  • Least favorite thing about dev: When code is time dependent so you can't put in breakpoints.
  • Tdd knowledge: Code is broken up into sections that you can independently test?
  • Why are you attending: It's one of my employee goals. I want to be more effective at my job and generate easy to read/modular code effectively
  • Back