I'd say I'm also just barely into Level 2 with a few of both extremes here and there.

Computer Science:
- data structures: log(n)
- algorithms: n
- systems programming: log(n)

Software Engineering:
- source code version control: n
- build automation: between n² and n
- automated testing: n²

Programming:
- problem decomposition: log(n)
- systems decomposition: between n² and n
- communication: log(n)
- code organization within a file: log(n)
- code organization across files: use n in practice for personal projects, but use log(n) for large projects
- source tree organization: log(n)
- code readability: n
- defensive coding: between n² and n
- error handling: n
- IDE: n, some log(n)
- API: higher n² to lower n
- frameworks: sadly, between 2ⁿ and n²
- requirements: log(n)
- scripting: n
- database: n²

Experience:
- languages with professional experience: uh... I don't really understand the question, so... 2ⁿ?
- platforms with professional experience: n, low end
- years of professional experience: n
- domain knowledge: n

Knowledge:
- tool knowledge: n²
- languages exposed to: mid-to-high n²
- codebase knowledge: log(n)
- knowledge of upcoming technologies: n
- platform internals: n
- books: log(n)
- blogs: between n and log(n)

If anyone wants to average that for me, go knock yourselves out

My average was somewhere around 1.7 if I calculated correctly. I had a lot of log(n) points but like 5 2^ns.

Edit: I did calculate wrong... it was actually 1.96, 1 "point" away from an even 2.

There are some pretty subjective things there, like you aren't a level 3 until you've tried GIT or programmed in Erlang or read a book on Forth.

Oh, I also need to improve my knowledge of more advanced data structures and algorithms (I can do hash tables, linked lists, trees, etc).

and they also missed out on 'has written a game'

... why would you even need an entire book on Forth?

I would say I'm a little bit between level 2 and level 3 but I did only a quick glance over most of the sections.

2.2 here. I found that a lot of these depended a lot on what you were working on, and not necessarily how well you work on it. It has a lot of good things to keep in mind, but it's definitely not a comprehensive test of ability.

Edit: Do you get bonus points if you kept track in a .txt then wrote a Ruby script at the end to grab your average score rather than do it yourself?

:3 Seems I'm a 1 across the board (with some 2s). Oh well, that means I have a lot of room for improvement.

Codebase and domain apply to the specific job you're applying for. So nothing you can say in general. Of course you could apply them to whatever project you're currently working on.

And defensive programming, doesn't the page explain what they mean by that?
It basically means that you don't just barge ahead implementing stuff. Being defensive means that you make sure errors are caught and/or handled.

Like what people often say around this forum, check the return values of allegro functions. Don't just assume they did what you expect just because they don't crash your program.

I must admit I suck at defensive programming, but I do know about it and if required by the man in charge I will apply it. Currently I am in charge and I'm lazy...

This matrix very clearly elaborates why I chose automation instead of computer science or IT. Making robots move is so much cooler than de-encabulating a database.