Course code: WEB-34
  • Years with company: 9
  • Years programming: 25
  • Primary programming language: C
  • Other programming languages: C++, Java, C#, Python
  • Unit test harnesses: Java J-Unit, but it's been awhile. In-house methods to test Asic design via Linux PCs and automated scripting.
  • Something else: I like to garden, lift weights.
  • Test practice now: For our C code, alot of times we have done manual unit testing, or pseudo-automated, more as the real device.
  • Target system: Embedded Fw running on ultra low power micros, such as ST micros.
  • Dev tools: Visual Studio C++ for Sw Apps, IAR Ide for Embedded Fw
  • Build time: 1-5 minutes
  • Coding standard: ansi-c, misra-c.
  • Function too long: > approx 30 lines or so, goes off screen. any function that feels like the equivalent of a run on sentence, with multiple subjects/themes involved.
  • Code reviews: We review C code for functionality, coding style, correctness on a regular basis.
  • Code time: 40
  • Test time: 40
  • Debug time: 20
  • Favorite thing about dev: Being able to create code to spec in an efficient, concise manner. It's also kind of fun just to code!
  • Least favorite thing about dev: The amount of test, debug time necessary to make basic code devoid of bugs, and operate smoothly, from a users perspective.
  • Tdd knowledge: The methodology seems to take more time up front to create, get in place, but once it's adopted, will probably save time and deliver more bug free code (up front), vs finding out issue later on.
  • Why are you attending: Get back into tdd concept and usage, and to know the benefits/drawbacks of using it.
  • Back