Course code: SP-CPP-4

Years with company: 1

Years programming: 10+

Primary programming language: C

Other programming languages: JavaScript, C#, C++, Assembler

Unit test harnesses: none/unknown

Something else: I've spent years doing end user support for nationally distributed products that run software I wrote. If they're gonna hot plug it you should try hot plugging it at least once before it leaves the building...

Test practice now: some of the legacy code here is tested using tools developed after Grenning training (10+ years ago?). I know zero details beyond: "the tests run at build time"

Target system: various embedded systems, more towards the 32 bit microcontroller

Dev tools: eclipse, xdc tools

Build time: 11-30 seconds

Coding standard: there is a modified Embedded C Coding Standard (Barr) applied to some legacy code

Function too long: too many arguments... runs off the screen in both x and y directions

Code reviews: informal if existent

Code time: 3

Test time: 3

Debug time: 3

Favorite thing about dev: seeing intuitive, useful electronic hardware work with high performance, despite the complexity

Least favorite thing about dev: legacy code mess. lack of documentation. overly complex solutions to simple problems.

Tdd knowledge: I read the first few chapters of the Grenning book years ago.

Why are you attending: I want to see generic TDD before figuring out how it was implemented here in legacy code