Course code: UBL-1

Years with company: 15

Years programming: 15

Primary programming language: C

Other programming languages: C++ Rarely

Unit test harnesses: N/A

Something else: N/A

Test practice now: JTAG, Logging, User Stress test: If it is something that user can trigger extenrnally I create a script test which stress my code from user interface.

Target system: Drivers for esystem embedded mainly (AMR technology, but not only).

Dev tools: Source Insight Editor heavely. ARM tool chaing for building and linking. gcc.

Build time: 30-60 minutes

Coding standard: In my job I had to review code and make change on it. Rarely I have to write code starting from scratch. Basically it is expected from me to be more engineer software and less pure programmer.So I try to follow the standard I find in the code.

Function too long: when I get lost between the line and I make heavelly use of mouse wheel (using 23 inch monitor)

Code reviews: The main focus during review is optimize it and simplifying it for better future reading.

Code time: 70

Test time: 10

Debug time: 20

Favorite thing about dev: Freedom and Creativity

Least favorite thing about dev: getting lost when the code starts to be too complicated to have a clear big picture. So I need to re-design again to make it simple.

Tdd knowledge: The acronym and an overview of the concept on the web.

Why are you attending: As far as I understood reading about tdd it seems this is going to change my paradigm on design method. So I'm curious to go deeper in this. Not sure if I'll ever use this, but, who knows, maybe yes. So I give to myself an opportunity.