Course code: WEB-35
Years with company:
Primary programming language:
Other programming languages:
Unit test harnesses:
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.
Medical device containing two microcontroller (one main, one supervisor) and bluetooth connectivity. It injects drug.
VS Code / Eclipse, Parasoft, C, Azure Dev Ops, conan package manager
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?
Done in Pull Request in Azure Dev Ops. Sometimes thorough, sometimes not.
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".
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.