Course code: BARR-4

Years with company: 5

Years programming: 11

Primary programming language: C

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

Unit test harnesses: None

Something else: I enjoy learning about new development techniques.

Test practice now: Functional test at a system level. Unit tests informally throughout development.

Target system: arc welding power supplies, Cortex M, C2000, Coldfire

Dev tools: Code Composer, Notepad++, Eclipse, Visual Studio

Build time: 1-5 minutes

Coding standard: Loose definitions on coding style that are not enforced.

Function too long: When it is difficult to test it.

Code reviews: Very informal over the shoulder reviews. Working to develop a formal process.

Code time: 50

Test time: 25

Debug time: 25

Favorite thing about dev: Debugging the hard to find bugs. Writing code that is well structured and well tested -- a work of art.

Least favorite thing about dev: Working with legacy code that is not well documented and difficult to test.

Tdd knowledge: Unit tests are written for code before it is actually written, then I believe the code is written to pass the tests.

Why are you attending: I asked to attend so that I could hopefully learn how to write code that is more easily tested and automate the test process to save time. Hopefully get more peace of mind when shipping software because I know that the code is well tested.