Course code: TH-2
  • Years with company: 20
  • Years programming: 40
  • Primary programming language: C
  • Other programming languages: python
  • Unit test harnesses: cmocka
  • Something else: My programming focus is on hardware related stuff of embedded systems, mainly audio.
  • Test practice now: 1) compiler as static code analyzer 2) cpp check as static code analyzer 3) source code review 4) manual tests 5) cmocka on a daily base via jenkins 6) system test cases on a daily base via jenkins
  • Target system: Embedded system with multiple cores, typically based on ARM 32/64 bit.
  • Dev tools: Source Insight Beyond Compare CPP Check
  • Build time: 5-30 minutes
  • Coding standard: Full awareness that the person who will maintain my code might be a manic serial killer who knows where I live. Never change the coding style of an existing file.
  • Function too long: If comments are needed which are not related to a single line.
  • Code reviews: Very useful. The skill is to invite people which are able to give useful feedback.
  • Code time: 20
  • Test time: 60
  • Debug time: 20
  • Favorite thing about dev: It is creative.
  • Least favorite thing about dev: If time or money are wasted for any reason.
  • Tdd knowledge: The idea is quite obvious. It is not the only but maybe the best way to get meaningful unit test cases. I would rate this a helpful if code is under your control. It is difficult to apply if only minor changes are added to a suppliers code.
  • Why are you attending: I get the chance to do this. Being a senior engineer team members ask me each day for help. If I am not trained I cannot tell what is useful and what is not useful. It is not the question whether it makes sense. I am convinced that it make cents :)
  • Back