Course code: TH-1
  • Years with company: 21
  • Years programming: 21
  • Primary programming language: c language
  • Other programming languages: bash, python (few), c++ (few)
  • Unit test harnesses: Sw Department wide: Jenkins, Bash Scripting, Artifactory for storing logs, firmware versions, crash dumps. I have only partially experience with Jenkins.
  • Something else: engineer for telekommunication, but not for informatik, I got used to programming in the company for hardware related topics, like power saving, battery charging and the last year to support the audio functionality in our projects.
  • Test practice now: As unit test with bash scripts, with intention for automatisation in CI (jenkins). If not possible only manually. Especially for audio topics to recognize if audio path really enabled we have few sensor options to realize woking software.
  • Target system: Embedded system with mostly ARM processor, main software delivered by processor producer, do we advancing the system and make it compatible in the customer environment.
  • Dev tools: Source Insight, Notepad++, propiritary tool of the the processer producer (Qualcomm, Mediatek), git (last years), before clear case as version management
  • Build time: 5-30 minutes
  • Coding standard: Department wide defined standard.
  • Function too long: At the moment it becomes unreadable or if it obviously that more functionalities are covered by on function. Review of sequences of the whole concept is very timerequesting and often no doable.
  • Code reviews: Reviews in git lab: Check for syntax problems or obviously better to handle functions. To get deeper in the right
  • Code time: 6
  • Test time: 2
  • Debug time: 2
  • Favorite thing about dev: To get features realized. To see final functionality.
  • Least favorite thing about dev: Build times, upload times, briefing of management about unfinished states.
  • Tdd knowledge: Nothing in detail.
  • Why are you attending: Delegation of software department.
  • Back