Course code:
ROL-1
Years with company:
8,5
Years programming:
23
Primary programming language:
c++
Other programming languages:
shellscript, javascript, java, some python, delphi (long time ago), worked directly with assembler for motorola 68k cpu's, visualdsp++ for analog deviced sharc dsp's, ...
Unit test harnesses:
cunit
Something else:
38yrs old
Test practice now:
mostly manual testing since it's mostly low level hal code that is highly dependant on real world timings/loads..
Target system:
currently an yocto linux embedded system; running on an single core arm cpu (cortex a15)
Dev tools:
nothing special; few editors, console, qtcreator, ms vs code, etc.
Build time:
1-5 minutes
Coding standard:
...
Function too long:
no real metrics, but when it starts doing subroutines that belong into a separate function/method...usually i try to keep functions below 50-60 loc
Code reviews:
unfortunately there are none
Code time:
60**
Test time:
20
Debug time:
5
Favorite thing about dev:
...
Least favorite thing about dev:
...
Tdd knowledge:
i could write a small essay about what i remember from university lectures about tdd, but to keep it short: first you define/write a test, then you write code that satisfies that test; refine and repeat.
Why are you attending:
improve my nearly non-existant tdd skils (really). i used unit tests on very few occasions, but i think it's a powerful "tool" to improve coding efficency and prevent unexpected behaviour...