Course code: NDC-2
  • Years with company: 16
  • Years programming: 31
  • Primary programming language: C
  • Other programming languages: Objective-C, Python, C++, Assembly
  • Unit test harnesses: Company internal
  • Something else: -
  • Test practice now: New code is tested using unit tests developed on Windows and executed on target. Legacy code is tested using manual test procedures.
  • Target system: PowerPC based real time controllers for automation and control systems.
  • Dev tools: WindRiver Tornado, Workbench, GCC, Testwell C++
  • Build time: 1-5 minutes
  • Coding standard: Avoid dynamic memory allocation during normal execution, allowed during reconfiguration phases. Mapping standard between object oriented UML models to C code.
  • Function too long: Nothing explicit. A function split into sub-statements (functions) rarely become very long.
  • Code reviews: Mandatory review by at least one other person. Now based on Git pull requests.
  • Code time: -
  • Test time: -
  • Debug time: -
  • Favorite thing about dev: To solve a problem.
  • Least favorite thing about dev: To solve the same problem again and again.
  • Tdd knowledge: I know the term and the concept.
  • Why are you attending: I work as an architect for a code base that has evolved since the 80s. I know the pain of lack of automated tests and the difficulty of introduced them later.
  • Back