Course code: WEB-35
  • Years with company: 2
  • Years programming: 5
  • Primary programming language: C
  • Other programming languages: C++ and VHDL
  • Unit test harnesses: CppUtest
  • Something else: I have started my career as a Hardware developer and decided to change to Embedded Linux device driver developer. After a year, I started to work with SoC (VHDL + Embedded Linux + C programming), where I spent 2 years. Nowadays I work mainly with C for embedded environments.
  • Test practice now: For newly created software units, unit tests are applied during development ( first the logic is implemented, then tested). For legacy code, tests are done by looking at the integration level.
  • Target system: Low power Microcontroller 32-bits.
  • Dev tools: Eclipse, IAR , Visual studio, azdo, EA. It depends on the project.
  • Build time: 1-5 minutes
  • Coding standard: We use Misra C standard and additional company-specific code guidelines
  • Function too long: When a function starts to have more than one scope and logic. Rule of thumb, around 50 lines of code.
  • Code reviews: Done via Pull request
  • Code time: 20
  • Test time: 50
  • Debug time: 30
  • Favorite thing about dev: The ability to create value by translating human needs into lines of code, that can be easily maintainable, scalable and flexible so that new needs can be effortlessly added to the existing solution.
  • Least favorite thing about dev: Nothing comes to my mind now.
  • Tdd knowledge: Improve software maintenance and flexibility
  • Why are you attending: I am very interested in the TDD approaches, but I am still not sure about the limitation and challenges of this approach.
  • Back