Course code: WEB-41

Years with company: 2

Years programming: 5

Primary programming language: C

Other programming languages: Python, C++, java

Unit test harnesses: We currently use googletest, but are likely going to switch to unity test.

Something else: I do not have that much experience with unit testing. I learned a bit about it in school, but there wasn't an emphasis on it, and we haven't had a huge emphasis on it at work either until recently.

Test practice now: We have a small suite of unit tests (not much coverage), and then we have a software quality team test many aspects of the functionality of the software. I normally verify basic functionality before even passing it off to them.

Target system: Currently an ARM Cortex M4F chip, but that may change in the future. Likely still ARM Cortex though.

Dev tools: VSCode as my text editer, ARM-gcc is the main compiler, proprietary tools are also used quite often.

Build time: 1-5 minutes

Coding standard: We have internal standards that we try to maintain, but it often times they are not very strict.

Function too long: Sometimes by feel. I believe we also have commit hooks that check function complexity.

Code reviews: We use gerrit for reviews. Code must be reviewed by someone other than yourself before submitting.

Code time: 25%

Test time: 5%

Debug time: 30%

Favorite thing about dev: I love seeing my software do what I want it to do. I like designing and problem solving.

Least favorite thing about dev: Having to use old legacy code and coding standards that don't make sense or limit functionality.

Tdd knowledge: From what I understand, you write unit tests based on required functionality, and then code after.

Why are you attending: My manager signed our team up. (That is the real reason, but I do think it is also a good idea)