Course code: BLUE-2
Years with company:
Primary programming language:
Other programming languages:
C, Matlab, Python, Chapel
Unit test harnesses:
I developed parallel simulation frameworks.
Test practice now:
Unit tests and system tests.
Real-time Linux based HIL systems.
QT Creator, GitKraken, Crucible
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.
For flight code, crucible. For simulation code, immediate peer review.
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.
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.