Course code: CARBON-2

Years with company: 0.8

Years programming: 25

Primary programming language: C++

Other programming languages: C, JavaScript, Python, Shell

Unit test harnesses: cmocka, CppTest, Unity, Cpputest

Something else: Worked in the software security industry for 15 years, passionate about 'beautiful', expressive, code. I also like asynchronous and functional programming.

Test practice now: Unit test, test applications, integration test as well as end-to-end test

Target system: Linux, Windows, MAC

Dev tools: git, gcc, Visual Studio, Visual Studio Code, vim, gdb, windbg

Build time: 1-5 minutes

Coding standard: Our team has code formatting guidelines (and a .clang-format file), when working with legacy code it is expected to follow the existing coding style.

Function too long: If indent level becomes excessive, say more than 3 levels. Or if a function does too many orthogonal things

Code reviews: We use gitlab for code reviews, must be approved by two peers before merging can take place. I would say people are pretty involved in our code reviews.

Code time: 40

Test time: 15

Debug time: 5

Favorite thing about dev: Producing elegant software designs

Least favorite thing about dev: How easy it is to get something wrong. Difficult to re-use code

Tdd knowledge: Write tests first, then implement the code to make the test not fail

Why are you attending: Rest of my team went through the same training and (they) believe it is a good approach