Course code: VOL-1
  • Years with company: 5
  • Years programming: 15
  • Primary programming language: c
  • Other programming languages: mainly c-sharp and python
  • Unit test harnesses: nunit, cunit
  • Something else: wannabe renaissance man, self appointed sw architect in my team.
  • Test practice now: component test/unit test, HIL test of ECU, system test of end2end functions with all related ECUs
  • Target system: Closed loop control system distributed on two I/O ECUs in the truck, running on MPC574x family CPUs
  • Dev tools: MS visual studio and Vector Autosar toolchain
  • Build time: 31-60 seconds
  • Coding standard: fairly standard
  • Function too long: intuition and the use of the DOTADIW concept (from unix philosophy) function length is also mentioned in the coding guide line.
  • Code reviews: it depends on who you ask to do the review, but ranging from only style to functional. in most cases, we do not review test cases.
  • Code time: 70
  • Test time: 20
  • Debug time: 10
  • Favorite thing about dev: I like making stuff
  • Least favorite thing about dev: often, we work with legacy code, adding functionality, then in many cases, developing boils down to "what to copy, where to paste". then you're not really making stuff.
  • Tdd knowledge: not to much, but I'd kind of like to think I employ parts of it in my daily work. test-cases are developed in parallel with the application iteratively with frequent builds.
  • Why are you attending: besides the obvious, to learn about the concept. if there is potential to improve our product and/or way of working with this concept, we should of course learn more. also partly, networking with other developers within the organisation.
  • Back