Course code: BAD-1
  • Years with company: .25
  • Years programming: 11
  • Primary programming language: C#
  • Other programming languages: Java, JavaScript, Python
  • Unit test harnesses: Visual Studio Unit Testing, NUnit
  • Something else: Entry-level Software Engineer with a strong background in the .NET framework. Former Air-Traffic Communications and Landing Systems Technician (ATCALS/RAWS/Electronics Technician) with the United States Air Force.
  • Test practice now: In all honesty, White-box unit testing post development.
  • Target system: All Badger Meter Flow Instrumentation Products
  • Dev tools: Visual Studio Professional 2015/2017, Visual Studio Enterprise 2017, Eclipse, NetBeans, Git Bash, TortoiseSVN,
  • Build time: 11-30 seconds
  • Coding standard: SOLID principles, units should be as dependency free as possible and single-responsibility. Code readability is a must and where possible functionality should be described in-depth through comments.
  • Function too long: "Code smell", but often issues are identified when function is broken into pseudo code and there are extra steps/redundant or when broken into pseudocode multiple steps support another step then this 'section' should be evaluated to be broken off.
  • Code reviews: Often review code for clarity and stream-lined functionality. Code should perform its function and perform it well.
  • Code time: 50%
  • Test time: 20%
  • Debug time: 30%
  • Favorite thing about dev: Always a challenge and the immediate satisfaction of solving problems/resolving a bug. As a former electronics technician I can appreciate when something works and works WELL with solid and sustainable resolutions.
  • Least favorite thing about dev: So many different ways to solve a problem, so many tools to use, and so many languages that can be implemented. I often find I lose focus out of curiousity and a desire to learn everything at once which can be VERY time consuming.
  • Tdd knowledge: Test-Driven Development is the practice of defining functionality first in how units or functions of code should be used and designing/building tests prior to development. This ensures the code developed aligns with the requirement with minimal bias
  • Why are you attending: Requirement from supervision. Although had I been prompted would have gladly enrolled myself as I have wanted to dig more into C++ and my formal instruction on TDD and agile has been very brief.
  • Back