Course code: WEB-9
  • Years with company: 1.5
  • Years programming: 15
  • Primary programming language: Perl
  • Other programming languages: Java
  • Unit test harnesses: Perl prove, Java JUnit, Ruby Test::Unit and rspec, a tiny bit of CppUTest
  • Something else: I've won awards for my bad poetry.
  • Test practice now: I test-drive if it's gonna matter. If it matters more, I test-drive more carefully.
  • Target system: no idea, Arduino or RPi maybe?
  • Dev tools: git, vim, make, Eclipse, clang
  • Build time: Under 10 seconds
  • Coding standard: Whatever the team agrees on (though I have my preferences)
  • Function too long: When my snap-judgment guess about what it does is wrong, or when I can't decide whether my studied guess is wrong or not
  • Code reviews: Reviewing afterward is too late. I missed the decisions as they were being made (or someone else missed mine). I prefer pairing.
  • Code time: 40
  • Test time: 50
  • Debug time: 10
  • Favorite thing about dev: Turning wants, needs, and wishes into reality to solve someone's problem. Feeling competent frequently along the way. Positioning myself well to solve their next problem.
  • Least favorite thing about dev: When I don't feel competent frequently enough. It's self-reinforcing and I have to bust out of that spiral, usually by clearing my head enough to pick something small and easy that I can competently do. When I succeed, that's self-reinforcing too.
  • Tdd knowledge: It saved my brain: http://www.schmonz.com/2015/08/12/tdd-saved-my-brain/ It helps me focus and stay focused: http://www.schmonz.com/2015/08/19/life-hacks-for-the-test-infected/
  • Why are you attending: I've never learned much C because I've never gotten to do anything interesting with it. If I knew how to test-drive C, I'm sure I could find interesting things to try.
  • Back