Course code: BARR-6
Years with company:
Primary programming language:
c, c++, matlab, simulink
Other programming languages:
Unit test harnesses:
I have been working as a software engineer in the US since 2004. I worked for 4 different companies and I have been mainly worked on application software, such as diesel engine control, transmission control, and crane control software. I also use c++ with Qt to write display software during the past 5 years.
In all my jobs, I use water fall (V-model) development process for the software development. The unit testing is normally performed on the test bench or the real machine, for example, a crane, a tractor, or a truck. And I have never used TDD.
Test practice now:
I use a simulator or the HIL (hardware in loop) in our software lab most time. And I have to use cranes to capture the faults that cannot be duplicated in the lab. The modules communicate to each other via CAN bus (CANOpen). I trace the data on the CAN bus to look for anything abnormal. I use Lauterbach debugger for debugging.
The unit testing is done by our team in India.
GCC compiler, Tasking C/C++ compiler, Qt, Lauterbach with Trace32, dSpace (HIL)
Our company's c/c++ coding standards
Function too long:
a function that does more than one thing; it has deep loops or deep nested if-else; or it duplicates the same logic as others.
We use Phabricator to do online review
Favorite thing about dev:
Write code and watch it works as expected on a target system.
Least favorite thing about dev:
Frequently changed the requirements and debugging.
Why are you attending:
To seek for a better software development approach to improve our software quality and meet deadlines.