I have nothing against World of Warcraft, but the Gamasutra editorial World of Warcraft Teaches the Wrong Things highlights one problem I have with the entire MMORPG* genre:
[WOW teaches players that] investing a lot of time in something is worth more than actual skill. If you invest more time than someone else, you "deserve" rewards. People who invest less time "do not deserve" rewards. This is an absurd lesson that has no connection to anything I do in the real world. The user interface artist we have at work can create 10 times more value than an artist of average skill, even if the lesser artist works way, way more hours. The same is true of our star programmer. The very idea that time > skill is alien.
Nothing demonstrates the massive disconnect between time, skill, and value better than ProgressQuest. My character SuperWumpus is on the cusp of level 86:
ProgressQuest does away with all that tedious gameplay grinding and lets us focus on what really matters-- levelling up. The game's Latin motto is quamvis progressio, which means "as much progress as you please." To further emphasize the point, the logo is two crossed swordsprogress bars:
You're fighting with time: the person who "plays" the most ProgressQuest wins.
This is something that the Pragmatic Programmers warn us about on slide 46 of their How to Keep Your Job presentation, which is about becoming a better, more deeply skilled programmer:
The EverQuest Syndrome is the same problem highlighted in the GamaSutra article: just because you spend a lot of time doing something doesn't mean you're doing it well. Here's a good example from Weinberg's The Psychology of Computer Programming:
Using this sort of measure, we can easily fall into believing that the worst programmers are the best-- because they work so hard at it. A case in point was a programmer who worked 14 hours a day, seven days a week, for eight weeks to get a small program running in a new installation. For his efforts, the company gave him an award for exceptional service. Shortly thereafter, another programmer (the first had been promoted to a management position as an additional reward) was tasked with making some additions to this program. He found that the program was such a confusing mess that it was easier to rewrite than modify.The rewriting and debugging took exactly one week, working normal hours. Even considering that writing a program for the second time is far easier, the difference is significant. Moreover, the new program ran eight times aster, took half the storage, and was half as many lines of code. Clearly, the first programmer had been rewarded for making a mountain out of a molehill. The discovery of this misapplication of management largesse led to a severe drop in morale.
If you want to "level up" in your IDE, you can't do it by grinding through all-nighters. You have to build your skill portfolio.
* I searched for this link and one of the top hits is this Wikipedia is a MMORPG article. I've often thought that online forums were, in essence, multiplayer games.
Posted by Jeff Atwood View blog reactions
« Sometimes a Word is Worth a Thousand Icons Error Codes Must Die »
And just to show I'm not singling out the WoW players in the crowd, here are my stats in Battlefield 2..
http://bf2s.com/player/wumpus/
.. which I spend FAR too much time playing.
Jeff Atwood on February 27, 2006 12:55 AMI couldn't agree more. And there's a quote from www.bash.org that always strikes me as awfully accurate, and you have reminded me of it with that last line. It goes like this: "IRC: Multiplayer notepad". =)
By the way, I'm a fellow BF2 player...
Picacodigos on February 27, 2006 01:16 AMMMORPGs: The genre for union shops and state employees! :)
Chris Nahr on February 27, 2006 04:05 AMWow. I've long drawn the analogy between playing most RTS and "adjusting a slider in Excel faster than the other guy", but Progress Quest looks fantastic.
I must organize my sweatshop to go play it for a while.
TristanK on February 27, 2006 09:33 AMYes, but the trick is knowing which developer you are. Effective or less-effective. How can you tell? I've thought long and hard about it and haven't quite come up with an answer. I *think* I'm an effective programmer, but I've never been sure.
Aaron Jensen on February 27, 2006 10:45 AM> I *think* I'm an effective programmer, but I've never been sure.
I'm pretty sure the ineffective developers aren't thinking about this, so you're in the clear.
Introspection is where it's at.
Jeff Atwood on February 27, 2006 12:14 PM| Content (c) 2008 Jeff Atwood. Logo image used with permission of the author. (c) 1993 Steven C. McConnell. All Rights Reserved. |