Course code: WEB-29
  • Years with company: 1
  • Years programming: 39
  • Primary programming language: C
  • Other programming languages: Python
  • Unit test harnesses: CppUTest
  • Something else: My company serves various retail industries in IoT. Earlier I worked for a German safety equipment manufacturing company to develop gas monitors for about 25 years. I enjoyed studying & using Humphrey's PSP there to gauge and improve my work quality. I've also enjoyed reading about TDD through your book. I used CppUTest on the job a couple of years ago for testing MSP430 C code, on target via a simulator.
  • Test practice now: We test using manual device and system tests.
  • Target system: It's a small portable embedded IoT device built with a commercial RTOS on an ARM M0+ chip. It senses the world and reports data periodically to a server. Low-cost hardware is a primary project driver.
  • Dev tools: a tailored eclipse with gcc-arm-embedded toolchain, plus Msys2 and Gcc on dev box for unit test. GitLab Runner.
  • Build time: 1-5 minutes
  • Coding standard: none
  • Function too long: looks longer than a page or does more than one job
  • Code reviews: nada
  • Code time: 25
  • Test time: 25
  • Debug time: 50
  • Favorite thing about dev: challenging myself to always learn something new, and to find good, simple solutions to common problems
  • Least favorite thing about dev: there's too much variety and churn in development systems, languages, tools and methods
  • Tdd knowledge: have read and used your TDD for embedded C book & Michael Feathers Working Effectively with Legacy Code, yet I still have trouble believing I'll ever write tests first before code.
  • Why are you attending: I'd like to learn better methods for setting up unit testing frameworks and approaching testing legacy code. I'd like to be more sure and have less pain in future projects.
  • Back