ok... let's return to our main topic...rememer my graduation project?! any other ideas out there?On 8/31/06, Conor Todd <
[EMAIL PROTECTED]> wrote:Not necessarily -- I regularly prototype code with function names, calling sequences and arguments before I actually write code. That way I can change the structure of the code before I write so much that it becomes difficult to change.
But I know what you mean -- there's usually great pressure to get things done immediately. - Conor
On 8/31/06, Dooma® <
[EMAIL PROTECTED]> wrote:I agree too with you on the importance of documentation, and i think no one can ever disagree on that...
However, documentation can't be a graduation project on its own, i'll have first to write some code then document it :o)
On 8/31/06, Conor Todd <
[EMAIL PROTECTED]> wrote:
I completely agree with you on the lack of respect for documentation's role in software development. Much like in a math proof or a professional chef's recipe, many important steps and assumptions are not documented because it's assumed that whoever's looking at the code can understand it trivially. The problem is that what is trivial for the creator of the code is probably utterly foreign to someone who doesn't have the creator's knowledge of the project.
If only software were like wine: it's only good once you can put it away for a long time, come back to it, and still find it completely approachable and pleasant. - Conor
-- "Thought is only a flash in the middle of a long night, but the flash that means everything."
- Poincaré-=-=-=-=-=-=-=-=-
I'm going to run the Houston Marathon, but finishing's not my only goal: help me raise money for cancer research!
http://www.active.com/donate/tnttxgc/tnttxgcCTodd
Thanks!
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
