Course code: WEB-35
  • Years with company: 2
  • Years programming: 1 1/2
  • Primary programming language: Python
  • Other programming languages: LabVIEW, C++
  • Unit test harnesses: PyTest, UnitTest
  • Something else: I am an Electrical Engineering graduate who shifted into Verification work and enjoys it more than what came before it. Programming was once a dreaded thing to practice but has become one of my favorite things to do.
  • Test practice now: PyTest, UnitTest, other test API, and trial and error
  • Target system: I am currently developing test software using a Windows 10 Lenovo x64 machine, but plan to create tests to be deployed and triggered on Raspberry Pi 4's for actual CDCI.
  • Dev tools: Visual Studio Code IDE, Thonny IDE (for Pi Pico or lightweight Pi 4 work), GitHub Actions
  • Build time: 1-5 minutes
  • Coding standard: I am usually writing interface code for equipment that's later tested so a standard is that regardless of the protocol being used on the equipment, we name our functions similarly. By doing this we basically know all functions for all equipment.
  • Function too long: When it does more than one thing towards the target.
  • Code reviews: I do not have code reviews as a Verification Technician.
  • Code time: 40
  • Test time: 40
  • Debug time: 20
  • Favorite thing about dev: Being able to create something very specific for an custom application. Later being able to modify my programs and reuse them for an entirely different application but slowly building a collection of personal libraries that make my job easier.
  • Least favorite thing about dev: Packaging, setting up environments, and troubleshooting something to later realize the problem was somewhere else.
  • Tdd knowledge: Off the top of my head, I understand it to be the practice of consistently testing every other line of code you write assuming everything is a modular piece.
  • Why are you attending: R&D Director (at the time, he is no longer with us), encouraged that the Verification Team attend along side the the Development Team due to how valuable it could be for overall progress made.
  • Back