I agree with this. What I learned while studying CS
in school is to design and document first, then code.
Many people can write programs but few programs are
easily maintained, mainly because they are poorly
documented. As a design is implemented, it may become
obvious that changes are needed and this is easily
done.
--- "Dr. Gerald N. Johnson, P.E." <geraldj@ames.net>
wrote:
>
> I've always found it far more productive to write
> the user/programmer's
> manual before writing any code. That way there's a
> known and relatively
> fixed goal instead of creating code because I can
> create code. The
> procedure also cuts down on "oops, I should have
> done that too" when
> doing the manual later.
>
> 73, Jerry, K0CQ
>
> --
> FAQ on WWW:
> http://www.contesting.com/tentecfaq.htm
> Submissions: tentec@contesting.com
> Administrative requests:
> tentec-REQUEST@contesting.com
> Problems:
> owner-tentec@contesting.com
> Search:
> http://www.contesting.com/km9p/search.htm
>
>
=====
-Bob Wooldridge KC0DXF
-Web Mail: kc0dxf@yahoo.com
-Web: http://www.qsl.net/kc0dxf/
-See Also: http://www.anet-stl.com/~mcsg/
-Via HAM radio repeaters in St. Louis: 146.85, 442.10
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
--
FAQ on WWW: http://www.contesting.com/tentecfaq.htm
Submissions: tentec@contesting.com
Administrative requests: tentec-REQUEST@contesting.com
Problems: owner-tentec@contesting.com
Search: http://www.contesting.com/km9p/search.htm
|