Course code: CARBON-2
Years with company:
Primary programming language:
Other programming languages:
C, Perl, shell (bash, ksh)
Unit test harnesses:
Catch, CUnit, CppUnit, CppUTest, gtest, JUnit, nose
I'm currently an automation engineer, but also have many years of experience as a developer (writing primarily C code in more recent years).
Test practice now:
Functional gray-box tests.
Linux (CentOS, Red Hat, ...)
cscope, ctags, gcc, vim
cstyle (in the past)
Function too long:
It becomes difficult to understand and difficult to test (particularly when thinking about negative/unhappy path tests).
Gitlab MR, Reviewboard, or other code review tools.
Favorite thing about dev:
I like solving interesting problems and writing software allows me to have the computer do the less interesting part of that work for me.
Least favorite thing about dev:
Legacy spaghetti code (followed by un-peeling the onion).
As a development process, it emphasizes considering how to test the correctness of the software before writing any code.
Why are you attending:
I enjoy learning new techniques and ways to improve my own workflow and skill set, and enjoy opportunities to grow/improve as an engineer whenever those opportunities present themselves.