Course code:
BAX-1
Years with company:
3
Years programming:
16
Primary programming language:
C++
Other programming languages:
C
Unit test harnesses:
None
Something else:
I manage the group, and don't develop anymore. Received my masters in Software Engineering in 2007 and am now helping to drive best practices in my organization.
Test practice now:
Multiple layers. Informal bench testing. Code analysis. Code Reviews. Manual integration tests. Coverage unit tests and some functional (requirements) tests using VectorCAST. Also manual functional tests (we have a separate group set up for this). Systems V&V. Algorithm verification tests automated in MATLAB/Simulink.
Target system:
4 boards, main target is iMX.6 based.
Dev tools:
Editors, Green Hills emulators, RTOS debuggers, VectorCAST.
Build time:
11-30 seconds
Coding standard:
Its defined but there are very few "shalls" and in general underdeveloped and under-utilized.
Function too long:
If I hear about it from developers :)
Code reviews:
Code Reviews on all code. Many sentiments that they are not that useful. We have certain personnel who analyze code for defects.
Code time:
25
Test time:
0
Debug time:
75
Favorite thing about dev:
Making hardware move and do stuff. Helping patients. Improving code quality.
Least favorite thing about dev:
Struggling to figure out what a method does. Worrying about the unknown rationale for why a method was implemented, and concerned that I might break that.
Tdd knowledge:
TDD is a method of development where tests are written first before code is developed, and results in short test-code loops. This aids in quickly recognizing when code breaks. TDD provides a means toward continuous integration.
Why are you attending:
Because I want to learn along with the team.
Back