Course code: SAND-1
  • Years with company: 6
  • Years programming: 14
  • Primary programming language: C
  • Other programming languages: C++/Bash/Python VHDL/Verilog
  • Unit test harnesses: QSPY
  • Something else: I also have experience doing FPGA and linux kernel module development.
  • Test practice now: Testing scripts which attach to the target via debug UART. These use python and Q_SPY
  • Target system: Cortex M0/M3/M4 and Xilinx Zynq
  • Dev tools: IAR/GCC SEGGER JTrace/Ozone for tracing
  • Build time: 11-30 seconds
  • Coding standard: A coding standard exists, but it's loosely adhered to.
  • Function too long: When it spans longer than the length of my portrait monitor or is littered with really long switch statements
  • Code reviews: Depending on the speed of the project, code reviews and architecture meetings are held with varying frequency.
  • Code time: 20
  • Test time: 30
  • Debug time: 50
  • Favorite thing about dev: Watching my code cause a desired effect on the target hardware.
  • Least favorite thing about dev: Hunting down really obscure (rare) memory corruption bugs.
  • Tdd knowledge: Co-Workers
  • Why are you attending: I have a lighter project load during this apocalypse.
  • Back