Course code: WEB-10

Years with company: 12+

Years programming: 20

Primary programming language: C

Other programming languages: python, c++, java

Unit test harnesses: gtest

Something else: I telecommute to Gracenote's bay area office from my house in Maine.

Test practice now: gtest unit tests (that often look more like integration tests), nightly runs of our sample apps, QA-run regression tests (cucumber).

Target system: I mainly focus on automotive head units, but the SDK I work on runs on desktops, in servers, on phones, etc.

Dev tools: MS dev studio, p4, araxis merge

Build time: 31-60 seconds

Coding standard: tabs, not spaces. ;) as we deal in C on often old compilers, it is pretty simple. but not sure how to describe it.

Function too long: if it is more than a couple screens (my font is big)

Code reviews: they happen ad hoc at the discretion of the developer. as a senior guy, I am often the reviewer - sometimes offline, sometimes via shared desktop. sometimes we have group-level reviews.

Code time: 40

Test time: 20

Debug time: 40

Favorite thing about dev: problem solving

Least favorite thing about dev: issues that aren't reliably reproducible (mainly race conditions)

Tdd knowledge: write unit tests first, see them fail, write code to make them work.

Why are you attending: it was suggested by my boss' boss. am definitely interested to see if we can figure out a good way to better TDD (and unit tests in general) for our complex SDK