Course code: BLUE-1
  • Years with company: 4
  • Years programming: Professionally, 5
  • Primary programming language: C++
  • Other programming languages: C, Python, C#, assembly
  • Unit test harnesses: gtest, cpputest
  • Something else: I've really got a thing for old computers and retro technology in general. I write GameBoy music.
  • Test practice now: By writing a sizeable chunk of code, backfilling unit-tests to exercise its nominal behavior & edge-cases, and then iteratively developing both tests and code together. This is not real TDD because my tests usually don't come first.
  • Target system: Embedded microcontroller
  • Dev tools: vim, and the compiler, that's pretty much it...
  • Build time: 11-30 seconds
  • Coding standard: In-house standard based on a combination of more common industry standards -- currently migrating to something that's more commonly used
  • Function too long: When it's grown to the point where it does a bunch of logically unrelated things.
  • Code reviews: all merge requests into our mainline development branch are peer-reviewed by at least 2 other developers
  • Code time: 40
  • Test time: 40
  • Debug time: 20
  • Favorite thing about dev: - Writing code that makes a useful impact on real world systems. - Code-reviewing -- it seems I always learn something new from seeing how other devs solve problems.
  • Least favorite thing about dev: - Gnarly toolchains & infrastructure - Other peoples' commits breaking my code
  • Tdd knowledge: It involves writing the tests first and then writing code that makes the tests pass.
  • Why are you attending: I've never used TDD for literally anything and I'm interested in giving it a shot.
  • Back