No posts yesterday due to exhaustion. I didn’t get home from a trip to Columbus, Ohio, until the middle of the night and spent yesterday slumped–well, as slumped as Becky would let me be.

Today, while reading some of my blog backlog, I found a programmer personality test linked to from Juuso at GameProducer.net.

Because you’re all dying of curiosity, my results are below.

Test Results

---

Your programmer personality type is:

   DHTB

You’re a Doer.
You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money.

You like coding at a High level.
The world is made up of objects and components, you should create your programs in the same way.

You work best in a Team.
A good group is better than the sum of it’s parts. The only thing better than a genius programmer is a cohesive group of genius programmers.

You are a liBeral programmer.
Programming is a complex task and you should use white space and comments as freely as possible to help simplify the task. We’re not writing on paper anymore so we can take up as much room as we need.

My actual Meyers-Briggs type back in 1995 was INFP, if I recall correctly.

My only complaints about this quiz were:

• In the question about what you’re most likely to do when presented with a complex task, I tend toward 50-50 design/coding, as I usually do an iterative agile process. A little design, a little code, a little debugging, a little design, and so forth. The design may involve speaking with subject matter experts, which is more likely to happen at work than with personal projects.
• In the third question (where do you spend most of your time), I probably spend most of my time writing and running unit tests. Coding becomes an extension of the unit test.
• The sixth question (how much time is spent planning), again I’m about 50-50. I’ve got a systems architectural bent–go ahead and ask some of my email correspondants–which expresses itself as a lot of design and planning time.
• In question 10, when I program, I would love to shut the door. At work, I’ll attend meetings or have phone conversations to define the requirements and rules of the enhancement or feature. At home, I just don’t get to program very much. When actually coding, I’ve usually got headphones on to shut out the world’s noises and drown out my tinnitus.
• Question 12, with the “better” implementation, is just plain cruel. The TDD adherent in me says the first is better as it fulfills the test accurately. The architect in my likes the second (lots of comments, reusable code, etc.), but at the same time, it’s a reimplementation of something simple and exemplifies overkill.