It’s always good to be reminded of the power of good writing, purely because it engages you and makes you want to read more, rather than shut off.
Here’s a review of a software development process book (“Dreaming in Code” by Scott Rosenberg, founder of that great webzine salon.com), written by the ever-engaging Joel Spolsky (of joelonsoftware.com).
The [Quick Context}(http://joelonsoftware.com/items/2007/01/02.html) and the Actual Review.
Even though it’s a little off topic, it’s relevant to user experience, because one of the key points is: make sure the concepts and interactions you are developing are things people actual want and can understand – rather than something that makes sense from a programming architecture point-of-view.
And there is also this gem about designing before programming and the need for solitary thought-space to do this:
[Error] Number two, you hired programmers before you designed the thing. Because the only thing harder than trying to design software is trying to design software as a team. I can’t tell you how many times I’ve been in a meeting with even one or two other programmers, trying to figure out how something should work, and we’re just not getting anywhere. So I go off in my office and take out a piece of paper and figure it out. The very act of interacting with a second person was keeping me from concentrating enough to design the dang feature.
What kills me is the teams who get into the bad habit of holding meetings every time they need to figure out how something is going to work. Did you ever try to write poetry in a committee meeting? It’s like a bunch of fat construction guys trying to write an opera while sitting on the couch watching Baywatch. The more fat construction guys you add to the couch, the less likely you are to get opera out of it.
At least turn off the TV!
