Course code: WEB-14
Years with company:
Primary programming language:
Other programming languages:
C++, C#, python
Unit test harnesses:
I studied Electronic Engineering in England before moving to Germany to begin work as a Field Application Engineer. I then changed my role to become Embedded Software Developer for the same company.
In my spare time I enjoy running, cycling and skiing.
Test practice now:
Unit testing after implementation
Low power, embedded, Arm-core microcontollers. Typically M0.
IAR, Keil, SVN, Unity, Jenkins,
We have a coding standard with a list of guidelines/rules for writing code. This was created within the team and reviewed as necessary.
Function too long:
When the function does more than one thing. When it's difficult to read/understand. Too much scrolling. Difficult to unit test
Code reviews are requested using Review Board. They are done within the team. Not really enforced, it's the responsibility of each team member to request a code review.
Favorite thing about dev:
Creative. Challenging. Solving problems. Always ways to improve and learn.
Least favorite thing about dev:
Often a difference between how I would like things to be done and reality.
Planning accurately is very difficult!
-Tests are written before implementation
-Interfaces must be well defined
-Code is written to make the unit tests pass
-Tests should be executed automatically and continuously.
-Changes to the interfaces require the tests to be updated.
Why are you attending:
We decided in our team that we would like to move towards test driven development. We want to do it correctly.