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
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
forget abour documenting... after all, i'll need something up and running for a demo, in addition to the fact that we are planning to finish the graduation project :o)mobile ad-hoc routing algorithms sounds interesting... have you got any resources about it?
i'm still searching for an idea, if
See, this is the problem with software education these days.
There is no way to demo the documentation..
I met a lovely woman from the Univ of Chicago who was doing
her dissertation on mobile routing a couple years ago, but
I'm afraid that I don't have any concrete leads for you.
Google is
Hello all,
I'm planning to work on my graduation project on Wireless
Sensor Networks, and I found that TinyOS is very famous in this field.
But I didn't decide yet what will be the project, and I need
to know the fields of research in WSN. Has anybody any recommendations or
ideas?
Someone once mentioned to me that documenting the TOS 1.1.x components
and interfaces would make a good masters project...
heh
MS
ps...mobile ad-hoc routing algorithms were also recent mentioned.
I know there's a lot of stuff done, in theory, for cell-phones and
stuff, but it might be
