Course code:
ROL-2
Years with company:
4
Years programming:
17
Primary programming language:
C++
Other programming languages:
QML, Java, JavaScript, C
Unit test harnesses:
GoggleTest, QTest, JUnit
Something else:
If i code more than 8 hours my head gets mushy and the resulting code is bad.
Test practice now:
Mostly by hand, because big chunks of the code are not testable apart from other big parts.
Target system:
weak hardware ARM device
Dev tools:
QtCreator, MySQL Workbench, Python- and Bash-Scripts
Build time:
11-30 seconds
Coding standard:
Qt Defaults
Function too long:
I prefer functions to cover about 1/3 to 1/2 of my (FullHD 22") display. At max the full display.
Code reviews:
Code Revies must not be done, but for middle to big changes i use them with other experts of this code modules. Usually I tell the colleagues how it should work and they comment. If needed, we do multiple rounds.
Code time:
50%
Test time:
25%
Debug time:
25%
Favorite thing about dev:
There is always something to learn and it is very satisfying to make code run more stable and/or faster.
Least favorite thing about dev:
Clustering in coding standards/style, bad testability and everything else that makes me invest more time in understanding what existing code is doing instead of woriking on a problem/bug/feature.
Tdd knowledge:
Wiriting tests before the program code. This means what exactly the code should do in the end must be known to develop a test that can 100% verify the code satisfy the requirements. There are multiple ways how to practically do this in a project.
Why are you attending:
There is always something to learn and it's better if the whole team has the same knowledge input than only a few of them.