Course code: BLUE-2

Years with company: 2

Years programming: 30+

Primary programming language: C++

Other programming languages: C, Matlab, Python, Chapel

Unit test harnesses: CPPUnit

Something else: I developed parallel simulation frameworks.

Test practice now: Unit tests and system tests.

Target system: Real-time Linux based HIL systems.

Dev tools: QT Creator, GitKraken, Crucible

Build time: 5-30 minutes

Coding standard: Blue internal code, although non-flight code is not as strict.

Function too long: That is function dependent. A procedural flow function is easier to understand than one with many nested if-then-else and multiple exit points.

Code reviews: For flight code, crucible. For simulation code, immediate peer review.

Code time: 30

Test time: 50

Debug time: 20

Favorite thing about dev: Software is a creative process where it absolutely is possible to make use of successes and learn from failures of the past.

Least favorite thing about dev: Reading badly written, badly designed or uncommented code. In a professional environment, code should be written so it is clear the programmer cared about what was being done.

Tdd knowledge: Very little. I feel that I make use of some aspects but that's through an organic approach as opposed to a decision in methodology.

Why are you attending: If this is a process that can be easily applied, then it will be useful. It is important that this is not an all-or-nothing technique as that will be hard to implement across all sections of development engineering.