Course code: JHAP-1
Years with company:
Primary programming language:
Other programming languages:
Vala, Python, C++, Matlab
Unit test harnesses:
Python's unittest, C++'s mock, GLib's gtestsuite
I like experimenting with cooking and nutrition, and seeing its effects on exercise performance.
Test practice now:
After code is written, I go back and write unit tests to verify functions and conditionals with expected outputs.
Most target systems are ARM-based embedded boards, ranging from snapdragon-like systems, to more GPU enabled, like TX2s.
Visual Studio Code, valgrind, gdb, vim, gitlab, mattermost
I follow GLib's coding standard for the most part. I think this could use an update.
Function too long:
I think functions should be concentrated on one idea, and either singularly do a single task or aggregate several sub tasks together into a convenience function. If this isn't the case, it is too long.
I usually code review other's code, and should spent more time doing this as well as have my own code reviewed.
Favorite thing about dev:
I like the freedom of expression, and trying to achieve elegance and simplicity, as well as correctness.
Least favorite thing about dev:
Tight deadlines. I want to be able to "do things right", but I'm often forced to move onto the next thing quickly.
It is a mechanism to thinking about, scope, and design your code with the test written first. The goal is to write a failing test, get it to pass, and refactor to the state wanted.
Why are you attending:
I'm interested in this paradigm in practice to potentially make it a standard for our development teams.