There's one sentence I remember from some Extreme Programming books I read:
"the customer only knows what he wants when he gets it"
:-)
On Tue, Apr 14, 2009 at 11:27 AM, Achim Schneider wrote:
> "Richard O'Keefe" wrote:
>
> > If you have a low level of trust, you'll need a great level of
> >
"Richard O'Keefe" wrote:
> If you have a low level of trust, you'll need a great level of
> detail, and it still won't help.
>
Heh. Keep your friends close, your enemies closer.
Freelancing, I was always paid per hour, not per feature. From my
experience, writing something like "The contractor w
On 11 Apr 2009, at 1:40 pm, Maurí cio wrote:
But I have an additional concern: to fit in burocracy. I need
to write a contract that someone else, who understands just
office applications, not software writing, will need to feel
safe enough with to sign it. It's not that important to have
a good
I'm an engineer, and as a programmer I'm just an amateur.
This easied things to me, since I could take decisions about
practices based on what made sense to me. But now I need
to take responsability for some formal programming tasks,
and I don't know which examples to follow.
I think such a con
