Course code: WEB-18
Years with company:
Primary programming language:
Other programming languages:
c, c++, bash, java
Unit test harnesses:
python's unittest, junit, pytest, nose, cppunit, cunit
Though I am currently writing software, my training is in Mechanical Engineering. Programming skills have always complimented other job responsibilities
Test practice now:
pytest is my go to lately.
I tend to work in systems testing lately, with a lesser portion of my development on posix environments
gcc, pytest, cppunit, pycharms, jenkins
My personal standards are all that I should comment on here. I believe that code should be literate, i.e. readable, and that the processes in play should support code scrutiny.
Function too long:
When my description of a function starts to include a compound statement, I become critical. When that description becomes multiple sentences I think about refactoring seriously.
I work in an environment in which a minimum of two colleagues have to review code changes. These reviews range in content from critiques regarding readability to compliance with safety standards and requirement satisfaction.
Favorite thing about dev:
I enjoy the development of working tools and products. These are finite goals within a project, serving greater purposes withing a program. I enjoy honing and using a craft.
Least favorite thing about dev:
I do occasionally get frustrated with poorly documented and unreliable code.
I have practiced a somewhat permissive form of TDD for many years, and am now working toward enforcing a consistent TDD approach in my development practices.
Why are you attending:
In order to smooth my understanding of TDD in embedded C, which I have read personally in the past, and to expand my wider TDD skills with a deeper knowledge of the practice. That's the real answer, I'm that exciting.