Course code: BLUE-1

Years with company: 2

Years programming: 10

Primary programming language: Java

Other programming languages: python, c, c++, rust,

Unit test harnesses: junit, pytest

Something else: I like to write and play music.

Test practice now: I write unit and integration tests for it.

Target system: ?

Dev tools: vim and make mostly. Sometimes the intellij suite.

Build time: 1-5 minutes

Coding standard: Personal or company? Related to testing or not? I'm a fan of code over configuration and that a good design and a testable design are the same thing.

Function too long: When it becomes difficult to read or understand.

Code reviews: We use them. I try to do mostly substantive comments, but sometimes the pedantic "too many spaces" or "brackets on the wrong line" slips through.

Code time: 50

Test time: 30

Debug time: 20

Favorite thing about dev: I like making things and helping people

Least favorite thing about dev: Sitting inside all day has some serious disadvantages.

Tdd knowledge: A fair bit from school. It's an excellent way to design software, esp. if you know "what your going to make before you make it." I think it can be used in lots of circumstances but not all.

Why are you attending: I'm curious about using it in "all circumstances" and I want to improve our controller testing (and write actual controller code, which hasn't really happened yet).