Course code: WEB-8
  • Years with company: 16
  • Years programming: 15
  • Primary programming language: C++
  • Other programming languages: C, Python, VHDL, Verilog, Tcl, MATLAB
  • Unit test harnesses: GoogleTest
  • Something else: Love SciFi, like photography, looking to improve my programming skills by contributing to an open source project and getting feedback from more experienced developers.
  • Test practice now: In the past I primarily wrote in VHDL for FPGAs where we selectively tested code using testbenches. This is all fairly analogous to unit tests. More recently I've been writing C for microcontrollers, C++ for the ARM-A9 processors in the Zynq SoC, and Python for test equipment. I'm struggling to use GoogleTest and abstract away the hardware specifics of the different devices.
  • Target system: Primarily the Xilinx Zynq-7000 series SoC
  • Dev tools: Visual Studio, Eclipse, SDK (Xilinx's port of Eclipse), XCode, Komodo
  • Build time: 11-30 seconds
  • Coding standard: We have a standard at work, but I don't follow it.
  • Function too long: When I can't easily understand what it's doing
  • Code reviews: We don't have code reviews.
  • Code time: 20
  • Test time: 50
  • Debug time: 30
  • Favorite thing about dev: The aspect of design and creating something new. I also like optimizing things.
  • Least favorite thing about dev: That we don't have a lot of strong software developers at the company and I often feel as though I'm stumbling in the dark.
  • Tdd knowledge: Right now I have a hazy understanding of developing unit tests to ensure proper working code before writing the code (or immediately after to test boundaries). I am struggling with abstracting away hardware-specifics, such as time, IRQs, etc.
  • Why are you attending: I want to use TDD to create better software, faster. I intend on taking what I learn here and making it mandatory for our upcoming projects.
  • Back