Course code: WEB-17

Years with company: 2

Years programming: 15

Primary programming language: c

Other programming languages: primarily python, perl, bash scripting

Unit test harnesses: cmocka

Something else: i play in a satanic pop-rock band

Test practice now: usually via automated unit tests on a build server

Target system: embedded devices, FreeRTOS as well as Linux on ARM

Dev tools: vim, assorted *nix tools, make, gcc, IAR, git,

Build time: 11-30 seconds

Coding standard: internal company standard that has evolved over time

Function too long: if it doesnt fit on one screen, it's too big!

Code reviews: using bitbucket, git-based pull request process. 2 approvals required.

Code time: 40

Test time: 10

Debug time: 50

Favorite thing about dev: We write code that control giant hydraulic robots. It is very fun. I generally enjoy solving challenging problems and working towards elegant solutions.

Least favorite thing about dev: Accurate requirements gathering from our typical clients (small company, mechanical engineering types) has been incredibly painful, historically. Managing dependencies is also never fun.

Tdd knowledge: i have a general working knowledge of it. I've watched a handful of Uncle Bob's videos and have successfully employed TDD practices into both work and personal projects. I would say i am on the beginner - intermediate spectrum of TDD.

Why are you attending: because my employer very rarely springs for training and so I am latching on to this opportunity! But, having said that, I am genuinely interested in furthering my TDD knowledge.