Course code: WEB-16
  • Years with company: 0.616
  • Years programming: 10
  • Primary programming language: C++
  • Other programming languages: matlab, python
  • Unit test harnesses: gtest
  • Something else: On my spare time I like to play board games with my friends.
  • Test practice now: mostly printf.
  • Target system: i.mx35 and STM32 with a ARM cortex M3
  • Dev tools: optima, visual studio, lauterbach debugger, keil ┬ÁVision, svn
  • Build time: 1-5 minutes
  • Coding standard: There seem to be a few different ones for specific platforms, but I'm not familiar enough with coding standards to describe them efficiently.
  • Function too long: when I decide it starts to look ugly and hard to follow.
  • Code reviews: send the code to a colleague who usually returns it with some critique, if a larger discussion is needed a forum for all developers is held every other week where such questions can be raised.
  • Code time: 34
  • Test time: 33
  • Debug time: 33
  • Favorite thing about dev: Problem solving, figuring out how make the different parts go together to make them do what I want.
  • Least favorite thing about dev: hard to debug intermittent errors keeping you up at night.
  • Tdd knowledge: A coding philosophy based on developing tests for your code as you go along in order to verify the function of each small part, and to stop to try to make the small part of code fail instead of instantly moving on to writing the next one.
  • Why are you attending: I'd like some inspiration as how to improve my coding and see a few tools that would allow it. Also getting some variation to my workday as I've been doing non coding stuff for a while.
  • Back