Course code: ETA-1
  • Years with company: 1
  • Years programming: 18
  • Primary programming language: c
  • Other programming languages: assembly, c++, python
  • Unit test harnesses: google test(used for 3 years), hands on Ceedling
  • Something else: I'm 38, father of 2 children, passionate by the connected world, I used to work on Bluetooth low energy product since 2010.
  • Test practice now: Due to time constraints. I'm testing in on emulator... Trying to write unit tests when/if there is a bug.. to show highlight the bug, and demonstrate the fix.
  • Target system: 8Bits EM microelectronic Coolrisc.
  • Dev tools: Eclipse and Winidea (Raisonance), I also used to work with IAR, Keil uVision, Code Composer Studin
  • Build time: 1-5 minutes
  • Coding standard: I'm pretty strict about coding standard, especially about naming, making short self descriptive function which does a single thing and can be easily tested,
  • Function too long: For low level function, if it does more than one thing. On higher level function if it contains too much conditions, doesn't fit on a standard display a standard 100% resolution
  • Code reviews: The software shall build and all the unit tests shall pass. Regarding the way I'm reviewing, code aspect and the atomicity of the commit are important in order to be able to focus on the implementation change.
  • Code time: 35
  • Test time: 40
  • Debug time: 25
  • Favorite thing about dev: Code writing is fun for me. I like to find the best design exchange with colleagues to achieve it. By the way I now tend to prefer the design , definition, aspect than the implementation itself.
  • Least favorite thing about dev: Having to debug/edit someone else's code which doesn't follow any standard or is of poor quality.
  • Tdd knowledge: I've been using it a bit 2010-2014 and heavily since. But min this company it is "new".
  • Why are you attending: To complete my current experience with TDD which I learned on the "Heap" within my precedent teams.
  • Back