Course code: WEB-19

Years with company: 3

Years programming: 8

Primary programming language: C

Other programming languages: Python

Unit test harnesses: None

Something else: I play the drums

Test practice now: - Run code online, and using text based logging, confirm that the expected output is obtained - Enforce correct behavior using assertions and catch assertions with a debugger

Target system: ARM Cortex M4 SPI, I2C Custom RTOS

Dev tools: Eclipse

Build time: 11-30 seconds

Coding standard: We have a formatting standard. The functional coding standard is enforced through code review and, for me, was learned through experience.

Function too long: A function is too long when its intent cannot be easily determined from reading it, or the function description cannot fully describe the function within a couple lines.

Code reviews: Code reviews require the owner to verify, another person to review the coding standards and functionality, and third person to approve the change.

Code time: 40

Test time: 30

Debug time: 30

Favorite thing about dev: It's like solving puzzles

Least favorite thing about dev: The parts of development that are not programming - Managing releases - Sprint planning - Parsing external requirements

Tdd knowledge: Very little, I have not tried it.

Why are you attending: To learn about and bring ideas to my team about a more concrete way of verifying code, with the intent of increasing software quality.