Course code: ROL-2
  • Years with company: 3
  • Years programming: 6
  • Primary programming language: C++
  • Other programming languages: python
  • Unit test harnesses: google test and a little bit of qTest
  • Something else: Actually, I have studied physics and unfortunately I have never attended to a computer science course. Therefore, I am missing a lot of theoretical background and learned everything from the practical side.
  • Test practice now: I am using google test. To bring the system in the right state and set the needed preconditions is most challenging for me. Furthermore, the test converage could (as always) be improved but lacks of setting up the test.
  • Target system: embedded linux with ARM processor
  • Dev tools: QtCreator
  • Build time: 11-30 seconds
  • Coding standard: Well.... there have been a few attemps to establish a coding standard in our project (documented on a wiki page). In the last week, we at least managed to integrate teamscale to have an static code analysis tool.
  • Function too long: If it does not fit on one screen, if it does too much stuff, if I don't understand it any more one week after implementing. I hate long functions.
  • Code reviews: My colleague and me are doing regularly code reviews on the component we are developing. It helps us a lot and it would be great if we have more of it in the whole project. First attemps are made by introducing merge requests.
  • Code time: 40
  • Test time: 20
  • Debug time: 40
  • Favorite thing about dev: You see a result at the end of the day.
  • Least favorite thing about dev: Bug fighting, especially if the bug is not reproduceable
  • Tdd knowledge: I must admit... not much... I heared of it and it sounds really interesting and promising.
  • Why are you attending: My boss says so. BUT. I am happy with it since this is my change to get some theoretical background and to use the theoretical skills right afterwards in exercises. This is much better than attending to a talk about TDD or reading “only” a book.
  • Back