Course code: WEB-35
  • Years with company: 2
  • Years programming: 20
  • Primary programming language: C
  • Other programming languages: Python
  • Unit test harnesses: pytest
  • Something else: I'm an embedded software engineer. I worked several years in with real time hard-constraint software for radio communication. I'm now working since 2.5 years in the medical field.
  • Test practice now: Depends on the project. In the project I am now: program the device, hope it works. The testing team will do the unit tests later.
  • Target system: Medical device containing two microcontroller (one main, one supervisor) and bluetooth connectivity. It injects drug.
  • Dev tools: VS Code / Eclipse, Parasoft, C, Azure Dev Ops, conan package manager
  • Build time: 5-30 minutes
  • Coding standard: MISRA C 2012 + internal coding guidelines
  • Function too long: The coding guidelines of the company says: max 100 lines, and I think there is a max of 3 indentations. But this is not checked. Usually it's more an impression: can my function be split into several smaller functions? Am I comfortable with it?
  • Code reviews: Done in Pull Request in Azure Dev Ops. Sometimes thorough, sometimes not.
  • Code time: 4
  • Test time: 3
  • Debug time: 3
  • Favorite thing about dev: It's "easy" to do anything.
  • Least favorite thing about dev: Depending on how the project is lead, it can go wild very easily and the "anything" of above can be changed to "crap".
  • Tdd knowledge: I used it in Python, but not as deeply as it is explained it your book. But I love the concept.
  • Why are you attending: My manager thinks it is good that the entire team attends it so that we will work better together.
  • Back