Course code: EMM-002

Years with company: <1 year

Years programming: 10

Primary programming language: C (Embedded)

Other programming languages: Python, C++, Rust, Bash

Unit test harnesses: CMocka, Twister, Unity, Pytest, and in-house Rust/Bindgen C framework.

Something else: I'm a big sci-fi/fantasy reader, love Sanderson books. Also big into video games and going to concerts!

Test practice now: Ideally, unit-testing off target HW, if "required", on HW. Integration testing using our QA team's harness, then any BLE SIG tests. I also will do some basic personal smoke testing of my features iteratively.

Target system: ARCv2 ASIC running BLE stack.

Dev tools: VS Code, GDB, gcc toolchain when building on Linux, Docker, Metaware toolchain when built on target.

Build time: 5-30 minutes

Coding standard: I try to prioritize readability and testability over any arbitrary cleanliness/conciseness.

Function too long: If a function can be broken into multiple logical chunks or operate on semi-independent data.

Code reviews: First, I review over the intent of the change, then I go over other things like readability, tests.

Code time: 40%

Test time: 30%

Debug time: 30%

Favorite thing about dev: Just a fun way to solve problems, feels very math-y to me which is a passion of mine.

Least favorite thing about dev: Resolving/investigating extremely long linker dependency chains.

Tdd knowledge: I've learned about it in the past and tried using it on smaller personal projects, not professionall

Why are you attending: Generally our FW team could attain a higher degree of testing discipline.