Course code: NIELSEN-1
  • Years with company: 5
  • Years programming: 1
  • Primary programming language: C (in the past) - I don't code at work
  • Other programming languages: PHP
  • Unit test harnesses: My team uses Junit for Java.
  • Something else: I currently lead a team of software developers who code backend systems in Java. I was an Electrical Engineer in college and used C before. I think I can learn the concepts and bring them to my team even if it's a different programming language.
  • Test practice now: My team uses unit tests, and we are developing fully automated integration tests. We also use simulators or Jmeter for load testing.
  • Target system: Jboss in a VM
  • Dev tools: My team uses Eclipse or Jboss developer studio
  • Build time: 1 day or more
  • Coding standard: Don't officially have one, but one of my senior developers has started reviewing code and suggesting standards as we go along.
  • Function too long: When you can't break it down any further into something that is a self-
  • Code reviews: One person reviews code and provides feedback. We don't do this often, but we are trying to get in the habit of doing so in a more agile manner.
  • Code time: 50
  • Test time: 30
  • Debug time: 20
  • Favorite thing about dev: Logical approach to solving a problem.
  • Least favorite thing about dev: Spending hours to find where the bug is. Spending a lot of time trying to get the environment working, rather than the business logic.
  • Tdd knowledge: Create test first, then code. Make a failing test, then get a test to pass, then refactor code to get all tests to work.
  • Why are you attending: I want to learn about TDD concepts, so that I can understand the benefits, the methodology, and bring back the concepts to my team.
  • Back