Course code:
PASA-3
Years with company:
8
Years programming:
15+
Primary programming language:
C++
Other programming languages:
Python
Unit test harnesses:
Boot Unit
Something else:
I'm planning to watch the new John Wick movie this weekend.
Test practice now:
Ad-hoc, primarily.
Target system:
Automotive Infotainment
Dev tools:
Eclipse, Emacs, gcc, gdb, python
Build time:
Under 10 seconds
Coding standard:
I wrote it based on Misra, Google C++, and a few others. Nobody follows it.
Function too long:
When it does more than one thing
Code reviews:
All check-ins must be reviewed. We use an online tool called Code Collaborator
Code time:
75
Test time:
5
Debug time:
20
Favorite thing about dev:
Writing elegant, robust software. I also love deleting code.
Least favorite thing about dev:
Other people's code.
Tdd knowledge:
As I understand it, the idea is to drive your development forward one test at a time. Start by creating a failing test case, and then implement just enough code to make that test case pass. Rinse repeat.
Why are you attending:
Honestly, I don't think TDD is a good idea. I am attending only on the off chance that I might be misjudging it. Also, with the company pushing TDD, I am obligated to at least understand the particulars enough to be able guide my team in using it.