Course code: BECK-1
  • Years with company: 8
  • Years programming: 16
  • Primary programming language: C#
  • Other programming languages: Visual Basic Delphi SQL JavaScript
  • Unit test harnesses: DUnit NUnit Test harness included in Visual Studio
  • Something else: I have programmed for different environments and enjoy positive feedback from customers that use the software.
  • Test practice now: I have in the past created unit tests as I write the code. Currently I have been manually testing the code after I write the code.
  • Target system: Windows 10 embedded
  • Dev tools: Currently I am using Visual Studio
  • Build time: 1-5 minutes
  • Coding standard: A standard should include rules to enforce maintainability, quality, and UI rules and not just code formatting rules.
  • Function too long: I feel that a function is too long if it is doing more than what it is intended to do (it can be broken in to smaller logical parts).
  • Code reviews: The code review consists of sending the code (differences report) to other developers to be inspected for defects and coding standard violations. Any findings are reported an then corrected by the developer.
  • Code time: 50
  • Test time: 20
  • Debug time: 30
  • Favorite thing about dev: I enjoy the challenge of developing software, as well as the satisfaction of creating a tool that people appreciate.
  • Least favorite thing about dev: The most difficult part of developing software is that we are not usually allocated enough time to develop it.
  • Tdd knowledge: I have done reading on extreme programming. I have seen how valuable unit testing is. I have tried TDD, by writing a test, writing code, then writing more tests, then writing more code.
  • Why are you attending: I have never officially been trained in tdd. I would like to learn the concepts of tdd in a formal setting by an instructor. I would like to see if my understanding and implementations are the correct ways to implement tdd.
  • Back