Course code: PRAQ-1
  • Years with company: 1
  • Years programming: 9
  • Primary programming language: c
  • Other programming languages: python, assembly
  • Unit test harnesses: JUnit (very basic, a long time ago)
  • Something else: I'm from Scotland (but now living Trondheim)
  • Test practice now: continuous integration test suite (I write tests to test HW, but they can often fail if there is a code bug, and I sometimes write a few unit tests for key functions, which also runs on CI on the test HW)
  • Target system: ARM M4 ASICs and FPGAs
  • Dev tools: SCons, GCC, GDB, Git, Stash
  • Build time: Under 10 seconds
  • Coding standard: Company wide standard traditionally ignored by department, trying to reverse that, and add additional department rules
  • Function too long: general impression, code review
  • Code reviews: vague guidelines of when they are required, usually 2 reviewers on a major change (except TCD additions/changes where they are mandatory, and should involve other testers and HW designers)
  • Code time: 50
  • Test time: 20
  • Debug time: 30
  • Favorite thing about dev: problem solving
  • Least favorite thing about dev: dealing with legacy code
  • Tdd knowledge: vague knowlege - a couple of lectures at uni (part of an outside subject comp-sci course early in an electronics degree)
  • Why are you attending: I write and maintain embedded C tests (to test the HW). I think TDD ideas could be applied to our tests. I think our test framework (lib functions, test framework, and possibly tests) could be more robust using TDD
  • Back