Course code: TH-1
  • Years with company: many
  • Years programming: even more
  • Primary programming language: C
  • Other programming languages: ASM, C++, CMM (JTAG debugger control scripts), Script Languages for Win Command/Power Shell and Linux Shells (Bash), Python, Perl
  • Unit test harnesses: Jenkins CMoka
  • Something else: I'm a specialist for hardware related software (Device Drivers in general, Interface Driver and Protocol (e.g. USB), Operating System) and system debugging (Multi-Core real-time debugging via JTAG, Post Mortem Analysis).
  • Test practice now: manually
  • Target system: Mobile Phone SOCs
  • Dev tools: several
  • Build time: 30-60 minutes
  • Coding standard: Most of the software we handle originates from external suppliers. We mainly commission and stabilize, only sometimes adapt or extend the software. We have a collection of articles relevant for our work in confluence.
  • Function too long: A function is to long if it is further divisible on a given abstraction level (or layer). Rule of thumb: a function should fit on a screen.
  • Code reviews: GitLab based merge requests documented in Jira
  • Code time: 33
  • Test time: 33
  • Debug time: 33
  • Favorite thing about dev: Always new challenges, never gets boring.
  • Least favorite thing about dev: Being given incomplete requirements too often.
  • Tdd knowledge: Start with describing testable functionality. Define Test Cases by splitting down functions as far as it makes sense from the point of view of the user/customer. Having defined Test Cases start thinking about software design and implementation.
  • Why are you attending: Because my department leader asked me to stand-in for a sick colleague.
  • Back