|
Sounds like a everyday song.
Wisdom is often meant as the ability and desire to make choices that can gain approval in a long-term examination by many people.
|
|
|
|
|
|
With out good specs and requirements documentation the mos talanted developer is useless.
When prediction serves as polemic, it nearly always fails. Our prefrontal lobes can probe the future only when they aren’t leashed by dogma. The worst enemy of agile anticipation is our human propensity for comfy self-delusion. David Brin
Buddha Dave
|
|
|
|
|
David Lane wrote: With out good specs and requirements documentation the mos talanted developer is useless.
You can't say that in general.
Tight specs and requirements "brought down from mount Sinai" (meaning fixed and unalterable as if given by God himself) can kill any project.
Most of the time, the users do not know what they wand, end even less how they want it.
And how could they know?
They are just now coming up with their ideas. No one did this workflow before (or else your project would be a waste of time, as the users would be better off using the existing software).
Their ideas are naturally vague, sometimes ill devised and often without knowledge how much work a feature would cost.
Several iterations could be needed to get to know which workflows are feasible and desireable.
And that can not be thought out in advance.
Let's think the unthinkable, let's do the undoable, let's prepare to grapple with the ineffable itself, and see if we may not eff it after all. Douglas Adams, "Dirk Gently's Holistic Detective Agency"
|
|
|
|
|
It goes without saying
WPF - Imagineers Wanted
Follow your nose using DoubleAnimationUsingPath
|
|
|
|
|
I agree, but would also add the competent managers. It is all about people, after all
|
|
|
|
|
I totally agree, if the developers don't/can't/won't create code that is easy to maintain it doesn't matter how competent management, how well the requirements are defined, etc...
jgehman
Software Engineer
|
|
|
|