Re^2: OT: Project clients

Cutting documentation to save time means only one person understands the application so pray they don't leave or die
That's not the developers problem, is it?

It is, because the only one who will understand the app is the developer. That means wasting a lot of time explaining the application, or becoming an extension of it; "Can you put these 2 MS-Word pages in our Content-management system? We can't remember how it works". In my experience developers hate doing that :-)

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Comment on Re^2: OT: Project clients

Replies are listed 'Best First'.
Re^3: OT: Project clients by trammell (Priest) on Oct 20, 2004 at 14:54 UTC
It is, because the only one who will understand the app is the developer. And it's not; it's a responsibility the business has willingly shouldered, and delegated to the programmer. I've been in this situation more than once--the business chooses to cut corners now, ignoring future costs. That is their perogative. But it is not (necessarily) the programmer's responsibility to set policy.	[reply]
Re^3: OT: Project clients by Anonymous Monk on Oct 21, 2004 at 08:12 UTC
I'd say putting in 2 MS-Word pages in a CM system takes X hours. Those X hours are of course billable. Or do you work for free?	[reply]
Re^4: OT: Project clients by Joost (Canon) on Oct 21, 2004 at 09:59 UTC
Money isn't everything :-) The point is that all of the developers I know (including myself) hate to do that kind of work, but if there is no documentation, there will be nobody else who knows how to do it. I'd rather do something interesting. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]