Course code: NEPT-1
Years with company:
Primary programming language:
Other programming languages:
BASH scripts, occasionally some flavor of BASIC, and I copy and paste stuff from the internet that is python :)
Unit test harnesses:
We've met before when I worked for a previous employer. A co-worker of mine and I had contacted you about Agile consulting, and you did a presentation to our management. I have also went through your TDD workshop at a Barr Group Defect Prevention training in Maryland several years ago.
Test practice now:
Manually constructed test programs (no unit-test framework) put together on a case-by-case basis that run natively or on target depending on the situation. We also perform integration testing that is occasionally automated using Labview.
Many of our systems have multiple processors. Most are bare metal systems, and we use a non-real time flavor of Linux.
CCS (for MSP430), Doxygen, Notepad++, Cygwin, GCC/MinGW, GIT/Bitbucket
We loosely follow the Barr Group standard. We are in the process of formalizing our internal standards which will likely include the Barr standard with some amendments.
Function too long:
Excessive nesting, requires scrolling (<25-30 lines), has clear logical breaks or sections that could easily be standalone inline functions.
Conducted within Bitbucket Pull Requests, with out of band verbal and slack conversations.
Favorite thing about dev:
The chance to be creative and construct something.
Least favorite thing about dev:
Fighting my tools, non-standard and confusing environments, poorly architected legacy systems that are a pain to extend or debug without massive amounts of overhaul, occasionally having to write software documentation in Microsoft Word.
Red, Green, Refactor.
Why are you attending:
We are evaluating different unit test frameworks. Cpputest is one of our candidates to explore using as a standard framework. I want to use it again since I haven't touched it since the last time I took your class.