Course code:
JHAP-1
Years with company:
2
Years programming:
10
Primary programming language:
C
Other programming languages:
C++
Python
Java
HTML/CSS/Javascript
Unit test harnesses:
In college we used Google Unit Tests briefly
Something else:
After / alongside my engineering career I want to be a professor.
Test practice now:
Basic unit tests for Python, static anaylsis tools for C.
Target system:
Primarily ARM platforms with a host of peripherals, something like an EFM32 or EFR32, as well as some FPGAs with hardcores like the Zynq.
Dev tools:
VIM+GCC (sorry)
IAR
Build time:
1-5 minutes
Coding standard:
I (try) to spend most of my time on a whiteboard planning out before I start to work. Much of this time is spent hunting down what the current code does.
Function too long:
When you can't describe the work it does in more than a sentence or two.
Code reviews:
I've pushed for some more formal review processes on programs to leverage our on-site Gitlab. So, an issue tracker is created as a work order, a merge request is put in and tracked by an engineer. Two other engineers have to review and approve
Code time:
30
Test time:
20
Debug time:
50
Favorite thing about dev:
The planning and architecture phase.
Least favorite thing about dev:
Understanding a design that isn't there, left by an engineer who has poor communication skills.
Tdd knowledge:
It's going to make me handsome and solve world hunger. (sorry for the delayed flight, hope you're having a good day)
Spend time upfront to plan and commit to tests, iteratively run them to make sure your code keeps its promises.
Why are you attending:
I want to follow best principles like these to be a better engineer, and to teach others around me. I like carrying lessons forward.
I hope to apply the skillset to other work with Python and C++ as well.