Course code: DEV-1

Years with company: 10

Years programming: 15

Primary programming language: C/C++

Other programming languages: GObject, (long-long time ago C#, Java)

Unit test harnesses: boost unit-test framework

Something else: 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)

Target system: linux, soft RTOS, userspace applications, audio streaming

Dev tools: gcc, gdb, customized Scons, QTCreator as editor, console, JIRA

Build time: 1-5 minutes

Coding standard: 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

Code reviews: we use 'reviewboard', RBTools, reviewing is done before commitment to SVN

Code time: 70

Test time: 15

Debug time: 15

Favorite thing about dev: finding the correct solution

Least favorite thing about dev: messing with log files and looking for errors

Tdd knowledge: - 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.