Course code: WEB-33

Years with company: 10

Years programming: 35

Primary programming language: C/C++

Other programming languages: Python, C#, Matlab, Java, (learning Rust)

Unit test harnesses: Microsoft .NetMicro Unit Test

Something else: I have most experience programming PIC microcontrollers and linux for arm chips. I also do some web programming with Python, and GUI development using QT.

Test practice now: separate binaries and test scripts

Target system: Linux on ARM SBCs, PIC Microcontrollers, and getting into ARM STMicro chips soon as well.

Dev tools: Visual Studio, VS Code, QTCreator

Build time: 31-60 seconds

Coding standard: MBARI develops prototypes, and have no coding standards that we are asked to adhere to.

Function too long: Usually when I can't remember variable names from the bottom to top, or when sections seem repetitive.

Code reviews: We typically do these ad-hoc, with usually 1 reviewer.

Code time: 40

Test time: 20

Debug time: 40

Favorite thing about dev: I've always enjoyed embedded software tasks, I/O, communications, and control software.

Least favorite thing about dev: Troubleshooting code at the debugging phase

Tdd knowledge: I understand the basic philosophy.

Why are you attending: To see how we can apply this to embedded software development at a workplace that only builds prototypes, often the phase to do a rev 2 of software doesn't get funded, so I'm hoping TDD can help me make better solutions on the first try.