Course code: NEAT-1

Years with company: 5

Years programming: 25

Primary programming language: C

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

Unit test harnesses: None

Something else: Interests in woodworking, fitness. I feed stray neighborhood cats.

Test practice now: Functional testing via external interfaces for larger code that crosses multiple modules. Utility executables that test specific functions and sequence of functions- Mainly success and fail cases.

Target system: Arm processor running QNX- a unix-like real time os, POSIX compliant.

Dev tools: Linux environment & vi.

Build time: 1-5 minutes

Coding standard: Follow format in existing code Explain thought process in comments Flow is to create design doc in wiki, do code/test, then integration test then function feature test before handing off to QA.

Function too long: One function for one operation. IF operation contains large blocks, those blocks would have to be broken down.

Code reviews: Use Stash side-by-side diffs for individual review. Depending on the complexity of the code, there will be a group review and comment

Code time: 20

Test time: 30

Debug time: 50

Favorite thing about dev: Form, function and a executing methodology to solve complex problems in software. Mainly like in the embedded/hardware level.

Least favorite thing about dev: Sudden slam at the end for testing. Being accountable for code not directly written by you.

Tdd knowledge: Pieces of this methodology is used by lots of people across industry. TDD is a way to formalize this and give it prominence in planning.

Why are you attending: Get idea of the methodology and how this can be rolled out in full spirit.