Course code: SP-CPP-3
  • Years with company: 3.5
  • Years programming: 16
  • Primary programming language: C
  • Other programming languages: C++, python, bash
  • Unit test harnesses: pytest, googletest, cppunit
  • Something else: I chose embedded as my career because I really liked working with FPGAs at university, but due to the job market situation in my country I have been working mostly with embedded software. I like the challenge of resolving HW/SW problems.
  • Test practice now: On my current python project (3D camera calibration analysis software) I use a combination of unit tests and manual testing. For the camera side we develop Linux drivers and c++ demo and test applications, and this is tested by developers.
  • Target system: Nvidia Jetson with Ubuntu Linux, but also other similar SoC Linux platforms (NXP, TI ...).
  • Dev tools: Visual Studio Code, Git, RhodeCode
  • Build time: 1-5 minutes
  • Coding standard: We have an internal coding standard but it is not enforced in my team.
  • Function too long: It doesn't fit on my screen or I can't follow it
  • Code reviews: They are informal if any, we have been exploring making it part of the process but no consensus yet.
  • Code time: 33%
  • Test time: 33%
  • Debug time: 33%
  • Favorite thing about dev: The feeling of mastery, establishing order & repeatability, problem solving, making things work.
  • Least favorite thing about dev: Working on low quality software that behaves erratically. Chaos that ensues when requirements change
  • Tdd knowledge: I read your book "Test driven development for Embedded C"; my previous job used TDD in automotive.
  • Why are you attending: I think my software development skills have been stagnating, I hope to do more coding and learn.