Course code: WEB-12
  • Years with company: 2
  • Years programming: 4
  • Primary programming language: C
  • Other programming languages: C++
  • Unit test harnesses: None
  • Something else: I sustain legacy code, wherein we have requirements to use TDD code when adding new features for rapid response projects.
  • Test practice now: Regression Tests
  • Target system: C166 uC, AVR Xmega
  • Dev tools: JTAG
  • Build time: 11-30 seconds
  • Coding standard: Since I am mostly sustaining legacy code, I follow the protocol that is already in place
  • Function too long: To be honest, not sure. I would frankly say, when readability or performance suffers for the intended purpose of that function.
  • Code reviews: We have informal reviews with my mentor and I, and formal reviews whenever I am publishing a new framework.
  • Code time: 40
  • Test time: 20
  • Debug time: 40
  • Favorite thing about dev: It is exciting to control something very efficiently, to see how the 'pixies' in a MCU work during run time.
  • Least favorite thing about dev: Changing requirements, working with legacy processors, and obviously over-buggy code.
  • Tdd knowledge: It is a tool used to develop tests prior to developing code, this leads to less bugs in the lifetime of the code, which means a less costly development process
  • Why are you attending: I am genuinely interested in learning TDD. So many electrical (not firmware) engineers blow of TDD as a bloated requirement. However, I believe there must be value, or else embedded people would not be interested.
  • Back