Course code: JHAP-1

Years with company: 5

Years programming: 15

Primary programming language: C

Other programming languages: Vala, Python, C++, Matlab

Unit test harnesses: Python's unittest, C++'s mock, GLib's gtestsuite

Something else: 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.

Target system: Most target systems are ARM-based embedded boards, ranging from snapdragon-like systems, to more GPU enabled, like TX2s.

Dev tools: Visual Studio Code, valgrind, gdb, vim, gitlab, mattermost

Build time: 11-30 seconds

Coding standard: 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.

Code reviews: I usually code review other's code, and should spent more time doing this as well as have my own code reviewed.

Code time: 70

Test time: 15

Debug time: 15

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.

Tdd knowledge: 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.