Course code: WEB-36
  • Years with company: 18
  • Years programming: 25
  • Primary programming language: C++
  • Other programming languages: Python, Java, C#, APL, ...
  • Unit test harnesses: CppUTest, xunit variations for C/C++, Boost Test, etc.
  • Something else: Think of myself as programmer of scientific instrumentation. (20 years) More of an Agile/Scrum trainer these days, wanting to get back to more programming again. Want to apply it to eco sustainability challenges.
  • Test practice now: Personal projects: largely TDD Professional projects: a bit of TDD
  • Target system: Current: Multi Arduinos used on a NASA project for photovoltaic R&D, to improve power output for the Lunar Gateway project. Simulated sun system for testing PV's on earth, plus balloons to 120,000 ft to calibrate things in space.
  • Dev tools: Eclipse, Arduino IDE,
  • Build time: 11-30 seconds
  • Coding standard: By discussion of three main people involved
  • Function too long: Lack conceptual. Duplication. Hard to test.
  • Code reviews: Rare. Usually when there are questions. Or at end of completion of a new feature area.
  • Code time: 30
  • Test time: 30
  • Debug time: 40
  • Favorite thing about dev: Creativity. Impact via important work. Fast feedback.
  • Least favorite thing about dev: Debugging. Hurriedly trying to learn necessary new things. Setting up complex toolchains before making simple progress.
  • Tdd knowledge: Many uses over the last 20 years. (simple level) Received training. Done training. Paired. Paired with Ward a number of times. Created a few simple test frameworks when one wasn't found. (Old Matlab, Basic) Made a variety of simple C/C++ frameworks.
  • Why are you attending: Increase fluency. What to get better at making rapid TDD progress in legacy codebases. Less late nights and weekends getting a framework in place...
  • Back