Course code: WEB-9
  • Years with company: 6
  • Years programming: about 10
  • Primary programming language: C++
  • Other programming languages: C, ARM Assembly, some C#
  • Unit test harnesses: NUnit
  • Something else: Work with RTOS and embedded systems in general
  • Test practice now: mostly manual, some automatic tests on a higher level. Automatic system level tests and integration tests where the target system is accessed from a PC. PC side runs NUnit but the tests are not what is normally called unit level tests.
  • Target system: All are ARM based, the one I use most Freescale ARM i.mx35 (ARM11) running Enea OSE RTOS. Some work on a i.MX51 (Cortex-A8) with WinCE
  • Dev tools: GCC toolchain, eclipse as editror, debugging in Lauterbach Trace32 using JTAG
  • Build time: 31-60 seconds
  • Coding standard: No strict standard, internally defined.
  • Function too long: We have way to long functions, there is no culture or talk about it within the group. I try instead to atleast make the code non-complex.
  • Code reviews: we do not perform them. I tried several years ago but there where no interest, but I think/hope this is changing
  • Code time: 40
  • Test time: 20
  • Debug time: 40
  • Favorite thing about dev: Technical challenge. I like embedded software because the abilities of the system are usually well defined and scoped. And I like to work on physical product.
  • Least favorite thing about dev: slow compile times, old toolchains, crappy debug-interfaces.
  • Tdd knowledge: I read your book, went on another more non-practical course. I have tried cyber dojo on my spare time and I'm interested, but I lack practical experience.
  • Why are you attending: I know our code has bugs, I'm tired of firefighting when the bugs affect the production line or similar. I want to be able to change the code without fearing that it will break somewhere.
  • Back