Course code: MAST-1
  • Years with company: 10
  • Years programming: 20
  • Primary programming language: C
  • Other programming languages: assembly
  • Unit test harnesses: none
  • Something else: Developed RFID readers used for access to buildings/car-parks but also reading e-Passports. Protocol conversions are not my favorite but i did quite a lot of those. Using firmware to control and act upon hardware is what I like the most in my job. I think programming language RUST might be the first serious candidate to be used for Embedded firmware development after C and assembly.
  • Test practice now: - Reviewing each others code - TiCS analyze tool from Tiobe (https://www.tiobe.com/tics/tics-framework/)
  • Target system: STM32L4, STM32F2, PIC24HJ, PIC18F
  • Dev tools: Eclipse + gcc, MPLAB X + XC16 + C18
  • Build time: 11-30 seconds
  • Coding standard: Try to get to level C or better (within TiCS analyze tool)
  • Function too long: Cyclomatic Complexity of more than 4 to 5 should be avoided (within TiCS analyze tool)
  • Code reviews: Using Gerrit server (https://www.gerritcodereview.com/) to review each others code
  • Code time: 40
  • Test time: 40
  • Debug time: 20
  • Favorite thing about dev: Bringing (embedded) hardware to live using firmware
  • Least favorite thing about dev: Depending on third party software/firmware (compiler libraries, CubeMX from STM, Harmony from Microchip, etc.)...
  • Tdd knowledge: It requires a different way of working on a project which extends beyond the software department. It is not easy to get the rest of the company (management) along in such a process...
  • Why are you attending: Getting legacy code unit tested. Don't know how to start at the moment...
  • Back