Course code: BARR-9
  • Years with company: 1.5year
  • Years programming: 20+ years
  • Primary programming language: C
  • Other programming languages: python, tiny bits of C++
  • Unit test harnesses: none... that's why I am here
  • Something else: I have been suffering at step 0 of working through your book. But I have read the book when it first came out.
  • Test practice now: Manually. Identify new test cases, see that they fail with the changes, add changes, and see thath they fix the problem. List them in commit message.
  • Target system: multi part system but both targets are ARM based. built under Mac and Windows
  • Dev tools: gcc as toolchain but some processors require Windows to be built completely
  • Build time: 31-60 seconds
  • Coding standard: Mixed. started with one and now moving to the company's internal standard (google's C/C++ )
  • Function too long: when it's over 1 page on the screen ~50-100 lines...
  • Code reviews: using Gerrit. Requires votes for code, build, verification, and test... we ignore test.
  • Code time: 30
  • Test time: 20
  • Debug time: 50
  • Favorite thing about dev: Making this happen
  • Least favorite thing about dev: ongoing changes, working with many people and we aren't aligned on how to get things done.
  • Tdd knowledge: Read your book and have wanted my team's to leverage this. I do this in a manual sense but automating it would make my team and I sleep better at night.
  • Why are you attending: If not now, when? Especially when I can't seem to get the tools installed It will add my skill set when I start managing my next team as well as my consultancy.
  • Back