Course code: GE-3
  • Years with company: 15
  • Years programming: 15+
  • Primary programming language: Visual Basic, LabView, C#
  • Other programming languages: C, PERL
  • Unit test harnesses: None
  • Something else: Software that I develop currently are small-medium applications for internal use. Automation tools, etc.
  • Test practice now: Consequences of bugs are low because software is for internal use by a small group. Testing is limited. I led MeterMate group years ago, and we did peer reviews of ALL code changes, and some white box testing, but nothing too structured.
  • Target system: Generally Windows applications, but interested in meter firmware
  • Dev tools: Visual Studio
  • Build time: 31-60 seconds
  • Coding standard: NA
  • Function too long: Should be limited to a single "function" or operation. Generally should fit on one screen.
  • Code reviews: Author of change sits down with printout and explains changes to peer reviewer line by line.
  • Code time: 75%
  • Test time: 10%
  • Debug time: 15%
  • Favorite thing about dev: Breaking down problems into logical pieces. I get a lot of satisfaction from creating neat, well organized, and maintainable code that solves a real business need. I enjoy solving problems for others with software.
  • Least favorite thing about dev: Documentation (other than code comments), spending too much time testing.
  • Tdd knowledge: Not much
  • Why are you attending:
  • Back