5 replies
February 2006

JeffC

For more on wicked problems, also see http://www.cognexus.org/wpf/wickedproblems.pdf

February 2006

codinghorror

So that’s your paper, Jeff? Interesting stuff. Can it be made available online in HTML format for easier access?

March 2007

stochastio

'Reminds me of maths, or writing, even. You can’t never jump directly to the solution a complete work until you’ve previously gone through a process of some kind. You have to get the data/content down to paper, work around with it, and then, and only then the solution will start to reveal itself. I’d say acknowledging this pre-condition to play around more or less improductively with the problem at hand is the first real step to really get things done (well).

This is so contrary to our popular conception of what makes a great programmer: easiness to do things quickly, without practically thinking, even. Speed really only happens once you took your time to solve that kind of problem before.

March 2007

AdamD

iI know from personal experience that I can never get very far without writing code to better understand the problem I am trying to solve./i

That makes me feel a lot better, knowing I’m not the only one!

December 2007

SameerA

Very good points my friend… Very different from waterfall style development