Course code: EMM-002

Years with company: 3

Years programming: 10

Primary programming language: C

Other programming languages: Python, basic C++

Unit test harnesses: N/A

Something else: I hope this training goes well

Test practice now: using the bluetooth qualification tests and verifying manually in specific instances

Target system: an embedded firmware system written in C running on target

Dev tools: visual studio code as an IDE, cmake to build the firmware, ninja as a compiler

Build time: Under 10 seconds

Coding standard: loose, I am not sure we have a formal document at least that I have seen. But generally consistent

Function too long: when a function generally does more than one large task, or can't be described succinctly

Code reviews: code reviews happen in PRs by the people reviewing the change, rather informally done asynchronously

Code time: 50

Test time: 20

Debug time: 30

Favorite thing about dev: I like the "puzzle solving" aspect, as well as knowing that everything happens for a reason

Least favorite thing about dev: wasted development and broken code as a result of not understanding the whole complicated system

Tdd knowledge: I am aware that it is a practice where the test case is written before the code is changed to pass

Why are you attending: Because I was invited mostly. I would like to learn about TDD, but unsure how I will actually use it