Course code: DEV-1
Years with company:
Primary programming language:
Other programming languages:
GObject, (long-long time ago C#, Java)
Unit test harnesses:
boost unit-test framework
I like embedded sw, C/C++.
Don't like that there is very little time spent on designing of it (design patterns, etc).
Test practice now:
manual testing, unit-tests (if there is time for that)
linux, soft RTOS, userspace applications, audio streaming
gcc, gdb, customized Scons, QTCreator as editor, console, JIRA
we rather have coding style: camelcase for C++, underscore for C, no gotos, no public members, readablity first, etc
Function too long:
when it is hard to follow what it is met for
we use 'reviewboard', RBTools, reviewing is done before commitment to SVN
Favorite thing about dev:
finding the correct solution
Least favorite thing about dev:
messing with log files and looking for errors
- testcases should be written before coding and after interfaces are established.
- if interfaces are altered then testcases must be changed as well.
- tdd produces test oriented code writing.
Why are you attending:
- to be able to write code that has better testability.
- to see development from different angle and to learn from it.