Course code:
ROL-3
Years with company:
3
Years programming:
25
Primary programming language:
QML + C++
Other programming languages:
Python
Unit test harnesses:
Google Test,
'homemade' Tools
Something else:
My background is the ruelless world of 'C' programming.
New tools and methods are well appreciated.
Test practice now:
As Qt is platform independent, tests by the developer are ususally done in a simultation environment on a Linux Server.
That is fast an convenient.
Only after successfully testing the code, the code is cross-compiled and flashed onto the embedded target device.
Target system:
Embedded Linux, ARM CPU,
Dev tools:
Everything provided by Qt (Qt Creator, Qt Designer, QML Profiler etc)
Valgrid, Lint, Jenkins, Git, Gitlab pipeline
Build time:
11-30 seconds
Coding standard:
-
Function too long:
If I as developer can not debug or even understand it.
Code reviews:
Very new. Not entrenched in mindset. Is seen by some as a hassle.
But that is the wrong attitude. Code reviews can not make sure code is error free, but helps with architecture, style and grave mistakes.
Code time:
70
Test time:
10
Debug time:
20
Favorite thing about dev:
Creativity, lot of different companies
Least favorite thing about dev:
Often lonely endeavour.
Bit nerdish
Tdd knowledge:
Not much
Why are you attending:
I strongly believe this company needs to double down on testing, otherwise quality of product will never improve.
Current focus on features is not working.
So I want to be part of the revolution, of putting test much, much higher in priority.