Course code:
TH-1
Years with company:
23
Years programming:
35
Primary programming language:
C
Other programming languages:
C++, C#, Assembler, Python
Unit test harnesses:
Self written, cmocka
Something else:
I am working as a SW architect and depending on the project, also develop components. Often analyzing issues with rare occurrences and develop test strategies for long term tests to find a solution.
Test practice now:
Test applications using the APIs of my code.
Target system:
Mostly embedded devices based on a ARM solution, with Linux or ThreadX.
Dev tools:
The toolchain for our targets based on the supplier delivery (SCons, bitbake, gnu compiler chain for the build system.
Lint and CppCheck for static code analysis.
Build time:
5-30 minutes
Coding standard:
Depending on the project, we use some team generated coding standards or we take over the standards from the supplier delivery.
Function too long:
When i have to scroll up and down too much to understand the code.
Code reviews:
We mostly use GitLab. On older projects based on ClearCase, we use a ms-word review-template.
Code time:
40
Test time:
40
Debug time:
20
Favorite thing about dev:
It's always a challenge to create new functionality, to create fast and short code, to create power saving enhancements.
Least favorite thing about dev:
Too much feature requests from the management without a real interest regarding the required efforts.
Tdd knowledge:
From my understanding: Define an API, create a dummy and test code for that and the next step is to realize the real functionality.
Why are you attending:
My team leader wanted me to attend and i want to see, if i already "live" the tdd approach (at least partially) and i hope to learn some more for approvement.