Course code: DYNON-2
  • Years with company: 11
  • Years programming: 15
  • Primary programming language: C/C++
  • Other programming languages: Routinely? None. As needed python, shell scripting
  • Unit test harnesses: Google Test, Boost Test. But these have been in personal projects. At work strictly CppUTest.
  • Something else: Though I involve myself as heavily as possible at the architect design level, I primarily work on the display level. Utilizing Open GL (one variant or another).
  • Test practice now: A significant amount of manual testing to validate graphics. I've recently mocked/stubbed the OpenGL ES 2.0 api allowing me to get more of this area under tests. This doesn't remove the need for manual testing of graphical elements however...
  • Target system: This varies per project. Currently my target is a raspberry pi compute module 1 running a customized version of Rasbian lite.
  • Dev tools: gvim, Visual Studio Code, gdb, git, and subversion.
  • Build time: 1-5 minutes
  • Coding standard: We don't have one.
  • Function too long: This is a gut feel. I try to eliminate duplicated code, and keep a function to accomplish only one task.
  • Code reviews: This changes based on the project. For one, there is no reviews that take place. For another we utilize git hub's pull request review mechanic with defined guidelines. We use other tools for other projects.
  • Code time: 60
  • Test time: 20
  • Debug time: 20
  • Favorite thing about dev: Intentionally left blank.
  • Least favorite thing about dev: Intentionally left blank.
  • Tdd knowledge: I understand the purpose, goal, and process of TDD. I'm already sold on it.
  • Why are you attending: There are some larger things I hope to see come out of this class. Personally, I want a better understanding of the implementation details of mocking.
  • Back