Course code: COB-1
  • Years with company: 3
  • Years programming: 20
  • Primary programming language: C
  • Other programming languages: C++, Python
  • Unit test harnesses: CxxTest, CppUnit, CUnit
  • Something else: Lots of previous experience in TDD in C++, but not in C.
  • Test practice now: ad-hoc module testing during development Overnight system regression
  • Target system: Various embedded targets, primarily x86 based running VxWorks or Linux
  • Dev tools: MSVC, gcc, Visual SlickEdit
  • Build time: 1-5 minutes
  • Coding standard: I think we have one.
  • Function too long: If it can't fit on screen, or if it is clearly doing multiple things (in which case it should be split)
  • Code reviews: Peer reviews including TA of whichever component is changed.
  • Code time: 20
  • Test time: 40
  • Debug time: 40
  • Favorite thing about dev: The creative side of it. I enjoy building things and getting them working.
  • Least favorite thing about dev: Not much really. The aspects I don't enjoy are mainly organisational and political. I don't really consider those "developing software".
  • Tdd knowledge: My previous organisation was big on TDD so I'm quite familiar. When I moved here I tried to instigate some TDD using CUnit (with another person also on this course) but quickly succumbed to "cucumber in the pickle jar" status.
  • Why are you attending: Initially I wasn't attending, only here due to multiple dropouts. But I hope to learn techniques that can be used to drive cultural change in our organisation, which is desperately required to improve the quality of our product.
  • Back