Course code: WEB-17

Years with company: 1

Years programming: 24

Primary programming language: C#

Other programming languages: Python, C, C++, JavaScript, TypeScript, Java, CLISP,

Unit test harnesses: CUnit, Pytest, MSTest, JUnit, xUnit, Jasmine, Mocha\Chai

Something else: I've spent the bulk of my career building business systems and I'm a strong proponent of TDD. The last year I've been writing embedded C applications and I need to understand how the concepts fit into that domain.

Test practice now: Automated tests

Target system: Linux micro services, running in docker, hosted on Arnouse BioDigital controls

Dev tools: (C tools listed only) Vim, You Complete Me, Nerd Tree, Syntastic, clang, clang sanitizers, clang tidy, lldb, valgrind

Build time: Under 10 seconds

Coding standard: It differs among teams

Function too long: when it has more than one responsibility

Code reviews: Pull requests must be reviewed before check in. Also, code is often critiqued during retrospectives

Code time: 80

Test time: 10

Debug time: 10

Favorite thing about dev: I love the variety of problems to solve, the extreme focus, and the feeling of being part of an industry that is constantly evolving and making the impossible happen.

Least favorite thing about dev: The overwhelming amount of communication and process involved as team size grows

Tdd knowledge: I've been a regular TDD practitioner for several years.

Why are you attending: I want expert advice on applying TDD to C code.