> > Given this disparity, it seems > > crazy that, at least in my experience, the amount of > > effort applied to documenting the plan is so much more > > than the effort put into documenting the final system. > > Spot on. Savvy project managers will plan time for > documentation after implementation. However, much of the > time re-assignment to other projects occurs and that > planned time is considered a luxury instead of a > necessity. I'd like one solid week after implementation to > produce design, run, etc. documents.
To turn things back around somewhat, what happened to the write documentation first, then write the source from the documentation? If something needs to be added (and who knows of a program where it doesn't?) then document it first?
As I understand it, this was one of the prime tenets behind literate programs like weave/tangle.
Also, how does this contrast with the "only document what's needed" mindset that most programmers end up in, because there's literally no time to do anything else? At what point does practicality kick in?
Flat View: This topic has 38 replies
on 39 pages
[
«
|
3233343536373839
|
»
]
Previous Topic
