Course code: TOP-1

Years with company: 13

Years programming: 13

Primary programming language: C

Other programming languages: c#, c++ (pre C++11)

Unit test harnesses: Unity

Something else: I do not like warm drinks.

Test practice now: Mostly using DLP (Debug Later Programming) approach. Have read your TDD using embedded C book and have tried to start implementing TDD using Unity. Time spent in development is very heavy in code to start, then most of the time is spent testing, then most of the time is spent debugging. Continuous testing with the same test set is not done.

Target system: Agriculture control systems and agriculture sensing applications.

Dev tools: MPLAB X IDE, Unity, MPLAB REAL ICE, Atollic TrueSTUDIO.

Build time: 1-5 minutes

Coding standard: Follow the coding standard guidelines for the OS we use. This way we can use the same guidelines to keep the code look and feel the same.

Function too long: If it does tries to implement more than one idea.

Code reviews: There is no code review process. Development team usually consists of one individual.

Code time: 30

Test time: 20

Debug time: 50

Favorite thing about dev: Creating of complex ideas and logic into a form that is readable, understandable, and hopefully does what you want.

Least favorite thing about dev: Too many opinions on how code should look, what functions/variables should be called and the 'proper' formatting.

Tdd knowledge: A bit. I have read your book TDD using embedded C and implemented some simple modules using TDD and Unity.

Why are you attending: I am interested in a TDD approach to writing software. I am also interested in learning strategies for building mocks and fakes for faster development of code blocks using a TDD approach.