Course code:
BARR-6
Years with company:
4
Years programming:
6
Primary programming language:
C
Other programming languages:
C++, Perl
Unit test harnesses:
n/a
Something else:
I am an Electrical Engineer by education.
Test practice now:
Benchtop Functional Testing.
Target system:
Prototype headlight systems
Dev tools:
IAR, KDS, CCS, CCES, MPLABX, LPCXpresso
Build time:
31-60 seconds
Coding standard:
Self-made with help from Michael Barr's C coding standard book.
Function too long:
When it no longer fits on a single 8-1/2 x 11 sheet of paper or when it is making too many decisions so that it cannot be followed easily.
Code reviews:
Almost non-existent - there's a lack of knowledgeable firmware developers.
Code time:
70
Test time:
10
Debug time:
20
Favorite thing about dev:
I love the freedom I have to be creative and the opportunity to create structure while solving problems. Coding is logic and order. There are few things more satisfying than creating a properly documented robust framework and watching it work.
Least favorite thing about dev:
Timelines are too short to properly document the process.
Tdd knowledge:
It's a way to write a minimum of code that is designed to pass specific tests. These tests ensure that the code is working as expected and provide a more maintainable and repeatable standard against which future changes may be measured.
Why are you attending:
I'm a bit of a one-man-show at my company and our customers are becoming increasingly interested in how we test our firmware. It would be helpful to have some sort of process to show them I adhere to.
Back