Course code: WEB-30
  • Years with company: 3
  • Years programming: 15
  • Primary programming language: C++ 11
  • Other programming languages: Typescript; Java;
  • Unit test harnesses: gtest; junit; FitNesse;
  • Something else: I am currently working as a Scrum Master with some focus on technical excellence. I like practising TDD. Every now and then I try ATDD as well.
  • Test practice now: Unfortunately I am not writing much code at the moment. But I try to do my best to get the teams running with TDD and unit testing.
  • Target system: At the moment our target system are several micro services within an internal IT department.
  • Dev tools: Mostly IntelliJ for writing Code. GitLab for building and deploying the artefacts.
  • Build time: 1-5 minutes
  • Coding standard: We try to stick to four rules of simple design. Some clean code principles like only 5 lines per method. Only two parameters. Intentionally naming of variables, methods, classes and so forth.
  • Function too long: 5 Lines of Code should be enough. We always try to keep our functions only 5 lines long.
  • Code reviews: We mostly try to do Pair-Programming
  • Code time: 20
  • Test time: 20
  • Debug time: 60
  • Favorite thing about dev: I like learning new things. With things I mean e.g. patterns, principles and so on. Last week we did a Kata and tried to only write code based on principles like balanced abstraction, step down rule and so on. I like refactoring of code.
  • Least favorite thing about dev: I don't like to convince people about TDD.
  • Tdd knowledge: I have read some books about it. "Test driven devlopment by example" - "Acceptance driven development by example". And I try to do my best to practice TDD as much as possible.
  • Why are you attending: I would like to see, hear and practice how TDD works from an expert. So not only from the books and self educated. One of my first jobs was about writing code for cashless payment systems. I would so embedded C/C++. So a perfect match.
  • Back