Course code: WEB-29
  • Years with company: 2
  • Years programming: 19
  • Primary programming language: C++
  • Other programming languages: Python, Go, C
  • Unit test harnesses: Unity, GoogleTest
  • Something else: Wes Montgomery is my favourite guitarist.
  • Test practice now: GoogleTest - I have unit tests integrated in some parts of some projects, but an uphill battle to incorporate it int
  • Target system: Mostly XMOS MCUs or embedded Linux targets.
  • Dev tools: gcc, vim, CMake
  • Build time: 1-5 minutes
  • Coding standard: Working towards adopting and formalising one
  • Function too long: More than two screens. Many of them are too long anyway.
  • Code reviews: Upsource - we have a language-agnostic set of acceptance criteria
  • Code time: 30
  • Test time: 30
  • Debug time: 40
  • Favorite thing about dev: Working through obscurity and indecision to develop a working, well-crafted system is really satisfying.
  • Least favorite thing about dev: Gumption traps are acutely painful.
  • Tdd knowledge: In principle, it structures development activity as a short feedback loop within a rigid and supportive mental model. In practice, it tends to encourage implementing programs as assemblies of implementations-with-interfaces.
  • Why are you attending: When I've been able to use it (i.e. in C++), it's been a really satisfying workflow. I want to discover good ways to introduce it into C-based development, and to gather ideas for adapting legacy code so that tests can be added.
  • Back