Course code: WEB-35

Years with company: 8-ish

Years programming: 40-ish

Primary programming language: C++ these days

Other programming languages: C, Java (and long time ago, Lisp)

Unit test harnesses: CppUTest

Something else: I'm passionate about developing quality software, done "right" the first time so it can be used forever. What better way to save time than to reuse software you know you can trust?

Test practice now: Unit tests are executed during the build. Higher-level tests are still largely manual and/or ad-hoc. I'm seeking to improve this at the organizational level.

Target system: Military vehicles, ranging from microcontrollers to desktop-level machines.

Dev tools: Eclipse.

Build time: 11-30 seconds

Coding standard: It's centered more around good software practices than syntax.

Function too long: When it's doing more than one thing (although "thing" isn't easy to define in this context).

Code reviews: We need better participation. Authors need to do a better job making it easier for others to participate. We also fundamentally need to reduce the need for them by adopting better, more modern practices that include a lot more testing.

Code time: 60

Test time: 20

Debug time: 20

Favorite thing about dev: The creativeness of a good design. Technical brainstorming sessions. Communicating verbally with others.

Least favorite thing about dev: Maintaining poorly-written software. Throwing documents over the wall. Doing anything that doesn't add value.

Tdd knowledge: My understanding is it's based on tight time loops between developing code and the associated unit tests. I'm a big fan of design-by-contract (interfaces first), so I'd like to get a better understanding of how these ideas relate.

Why are you attending: As a new technical lead at the organizational level, my goal is to bring automated testing into our processes at every level. I see code-level TDD as one piece of that, and I'd like to get ideas for extending those techniques to higher levels.