Course code: NEPT-1
Years with company:
Primary programming language:
Other programming languages:
C++, C#, python, bash, LabVIEW, ASM
Unit test harnesses:
I like hiking and camping and reading. I'm a cat person, but I'm stuck with a Jack Russel Terror (spelling intentional) that came with the wife. :)
Test practice now:
Automated testing is handled by TeamCity. Manual testing is handled by our electronics lab technicians (we write a work order, someone picks it up, etc). We have a mix of unit tests, on-target tests, and static analysis. The amount of that depends on the project. Most of the unit-testing was implemented by a contractor. We've done some maintenance, but almost no expanding on that. We have a few on-target tests that we've implemented, but they are mostly black-box style tests.
Mostly bare-metal, 8051 or ARM.
Keil uVision, IAR, CCS, Simplicity Studio, gcc+make, Visual Studios, LabVIEW
We have an ignored legacy coding standard, we're in process to develop a new one based on Barr.
Function too long:
When I can only see less than half on screen, it's probably too long.
We use crucible or bitbucket, depending on whether the project has been ported from SVN to git.
Favorite thing about dev:
I like solving problems and I like the satisfaction of writing something out that fixes the problem.
Least favorite thing about dev:
I hate fighting tools. Fixing something in one tool shouldn't lead to a break with another, but sometimes it does.
Not a lot. My impression is that you write a test before you write a function. Make sure the test is failing, then go on to work on the function until all tests pass. Then move onto the next function.
Why are you attending:
I want to be doing TDD, but I don't feel like I have the time to learn outside of dedicated training time.