Course code: WEB-16
  • Years with company: 2
  • Years programming: 20
  • Primary programming language: Python, C
  • Other programming languages: Lua, PHP, javascript (?)
  • Unit test harnesses: gitlab CI, buildbot, jenkins, cron... dont remember. But CI is a real time saver.
  • Something else: I'm tall, 1.90m and have a great sense of humor :)
  • Test practice now: nose2 for python or make test for C. Local gitlab server with CI. Use pylint or flake8 as a linter for python. I would love to have a good linter for C. Always compile with -Wall -Werror in CI.
  • Target system: x89, arm, blackfin
  • Dev tools: vim, cscope, ctags. Sometimes an IDE like pycharm. depends on language,codebase and build system. Have started to look into docker but have not had the time to do anything usefull with it.
  • Build time: 1-5 minutes
  • Coding standard: Varies on codebase and language. But I like consistency in the code.
  • Function too long: 20 lines or 5-6 variables? As small as possible but don't over do it. Readability and scope is King.
  • Code reviews: I love constructive criticism. It helps me grow and improve.
  • Code time: 70
  • Test time: 10
  • Debug time: 20
  • Favorite thing about dev: The only thing worse then programming is not to program.
  • Least favorite thing about dev: The only thing worse then programming is not to program.
  • Tdd knowledge: Have used TDD extensively in Java, ROR but not so much in C. It has many great uses but I often find system testing to be more time efficient in C. But designing for testability is very good design.
  • Why are you attending: "If I have seen further it is by standing on the shoulders of Giants". I have learned much in the past from reading code of really skilled programmers. And I always strive to improve my own code.
  • Back