Course code: AS-2
  • Years with company: 7
  • Years programming: 15-20
  • Primary programming language: C
  • Other programming languages: C++, Assembly, Python, bat-script
  • Unit test harnesses: google test framework
  • Something else: Self-educated programmer
  • Test practice now: Mostly with manual testing
  • Target system: AVR, ARM, x86, x64
  • Dev tools: Git, Visual Studio, clang-format, qt creator (PuTTY, RealTerm, HxD)
  • Build time: 11-30 seconds
  • Coding standard: Working code instead of following all standards (some shortcuts).
  • Function too long: Functions should not be more than one or two pages/screens long (except for very long switch cases). They should only do one thing.
  • Code reviews: When I review others, I usually focus on execution speed/avoiding bloated code. I also enjoy code that looks tidy, and testable, if possible.
  • Code time: 40
  • Test time: 20
  • Debug time: 40
  • Favorite thing about dev: Problem solving, understand how system works, dig into the low-level stuff, solving things at high-level
  • Least favorite thing about dev: Bloated and inefficient code. Long compile time. Ugly code. Getting many people to agree on a common standard.
  • Tdd knowledge: Some minor experience with google-test, but not used it actively. perhaps some minor experience during education.
  • Why are you attending: Learning how to use TDD effectively, in a way that fits my projects.
  • Back