Course code: BAX-1
  • Years with company: 1.5
  • Years programming: 24
  • Primary programming language: C
  • Other programming languages: C++
  • Unit test harnesses: VectorCast
  • Something else: Worked on both highly regulated and unregulated systems.
  • Test practice now: Functional testing using actual system HW and events that drive all paths to uncover all timing dependent race conditions to determine sufficient margins.
  • Target system: No OS
  • Dev tools: Oscilloscopes, LA, in-house tools
  • Build time: 11-30 seconds
  • Coding standard: boiler plate-ish with not enough examples
  • Function too long: Depends on complexity but generally like to keep below 30 lines
  • Code reviews: too much focus on syntax/coding-std and not enough on overall structure of design
  • Code time: 30
  • Test time: 60
  • Debug time: 10
  • Favorite thing about dev: Problem solving
  • Least favorite thing about dev: Separate reporting structures are used hide behind scheduling and system issues.
  • Tdd knowledge: Shifts time resources on completing a design and testing before coding the design. In theory, less time spent debugging issues... at least academics say without considering the moving requirements and undocumented and/or changing HW behavior.
  • Why are you attending: Learn new tool for designing, implement and updating UT protocols in different UT tool than VectorCast (as directed by management).
  • Back