Course code: ROL-3
  • Years with company: 5
  • Years programming: 35
  • Primary programming language: C++
  • Other programming languages: Python, Javascript, Typescript, C, Lisp, Dart
  • Unit test harnesses: QtTest, googletest, CppUnit
  • Something else: Nothing special
  • Test practice now: I am working most on legacy code, try to write some kind of unit tests to prevent regressions.
  • Target system: Embedded System, working with C++ / QT / QML
  • Dev tools: QtCreator / gcc / clang (code analysis), git,
  • Build time: 11-30 seconds
  • Coding standard: I try to use the coding standard of Qt for the c++ / QML coding. Otherwise it depends on the current coding standards for the module I am working on (can be different)
  • Function too long: It depends. Generally spoken a function/method shouldn't be longer than 30 lines.
  • Code reviews: We started doing merge requests with coding reviews
  • Code time: 40
  • Test time: 20
  • Debug time: 30
  • Favorite thing about dev: Been creative to find clean and efficient solutions for a given problem.
  • Least favorite thing about dev: Working on legacy code (brown field) without having the chance to make it better.
  • Tdd knowledge: Some basic thoughts about
  • Why are you attending: I would like to find a way how to write code up from the beginning in a better shape than now. I would like to get some ideas / tools how to refactor legacy code in an easier way than now
  • Back