Course code:
WEB-31
Years with company:
10
Years programming:
18
Primary programming language:
C
Other programming languages:
Python
Matlab
Unit test harnesses:
none
Something else:
Controls engineer primarily
Test practice now:
Mostly final testing of functionality and code reviews
Target system:
see Eric Renger's answer.
Dev tools:
Code Composer
ST's IDE
Build time:
5-30 minutes
Coding standard:
rules for variable naming, returns, globals, etc. Avoid div by 0s, infinite loops.
Function too long:
When I can't easily trace a variable's progression through the function.
Code reviews:
We review for coding standards as well as for functionality and efficiency, though much of our functionality is tested in system tests.
Code time:
20
Test time:
50
Debug time:
30
Favorite thing about dev:
I like the problem solving aspect of trying to get a robot to do what you want it to do with logical statements.
Least favorite thing about dev:
Choosing the right data structure or approach to a problem.
Tdd knowledge:
Mark gave our team a summary a few years ago after he attended this class. I have read some information, but have not implemented a test system.
Why are you attending:
Relying on system level testing and how a device feels just isn't sufficient. We spend too much time checking for things manually that should be done automatically, and I don't want to have to do those manual checks anymore.
Back