Course code: WEB-28
Years with company:
Primary programming language:
Other programming languages:
Unit test harnesses:
I love both cats and dogs!
(Note: Working on incremental enhancements to a "legacy" system and with work that's ramping up - that's why the % of development activities below may seem really skewed).
Test practice now:
Using a custom embedded unit test harness, after the code is written (I'd like to change that!)
Embedded, size constraints
Minimal, coding standard "by example" (supposed to be based on what Uncle Bob suggests in Clean Code?), so nothing enforced in an IDE
Function too long:
There are probably several different signs. One is when unit testing, there are several different disparate outputs and output paths - in other words, it doesn't do just one thing.
We've been having working meetings over video conferencing SW where the SME goes over the code with those less experienced and also makes changes. Also, we're looking at tools that integrate w/ our ALM tool for more traditional, reviews.
Favorite thing about dev:
It's exact - given input(s), you get expected output(s).
Least favorite thing about dev:
Sometimes (often), work takes more time than anticipated.
A good amount - I've used it in the past when I used to develop web applications and desktop applications using Java.
I've also taken some informal training on it (non-embedded, non-C++) and it was covered a little bit in a CS graduate course.
Why are you attending:
I want to learn how to do TDD in an embedded setting and bring back the ideas and knowledge to my team. We are currently using a custom harness that's HW-dependent. I also want to learn about TDD for C++.