Course code: AS-1
  • Years with company: 0
  • Years programming: 13
  • Primary programming language: C++
  • Other programming languages: C, RUST, ASM
  • Unit test harnesses: Gtest, Gmock, munit (unit with a greek mu)
  • Something else: I'm also a musician, I enjoy running and the outdoors. I read a lot of books. I enjoy making hardware-firmware hobby projects in my spare time with micro-controllers and embedded linux systems.
  • Test practice now: GTest
  • Target system: Not sure, I'm a new engineer at this company.
  • Dev tools: VSCode, mingw, gdb/make/ninja, arm toolchain.
  • Build time: 1-5 minutes
  • Coding standard: Not sure, I'm a new engineer at this company.
  • Function too long: Too many levels of indentation. Or - it's difficult to unit test (in that it's difficult to test it as one "unit", and requires convoluted integration-level tests to cover all codepaths.
  • Code reviews: Not sure, I'm a new engineer at this company.
  • Code time: 40%
  • Test time: 40%
  • Debug time: 20%
  • Favorite thing about dev: Solving complex problems, and the joy of a functioning system.
  • Least favorite thing about dev: Time constraints!
  • Tdd knowledge: I've watched (and read) some Uncle Bob (Robert Martin), and his red-green-refactor method. I also followed strict TDD methodologies at my previous company.
  • Why are you attending: Self improvement (really!). I've seen the direct benefit of TDD in embedded systems at my previous company, and would like to continue my growth in this area. Now that I have this knowledge, working in a legacy untested codebase is so nerve wracking.
  • Back