> I don't think grunge work is bad if the result is usable. Hence, what I > am trying to evaluate via the discussion is whether the result is > something that can actually be used by developers.
The thing about grunge work is it always takes far longer than you think it would. Besides, when you enter the real world you will have plenty of grunge work to do. Why get a head start on it?! > > if you aim to finish in about 2 months, you should be done in time in 4, wi > th write-up. > > a modular project is always good, so if you've actually got spare time > > at the end, you can add another component. (for instance, if the project > > is split into 9p server and 9p clients, you can add a different type of cli > ent > > for the same service.) I will second that. You can use any remaining time for all sorts of things -- there is always something more to do. Long ago a famous engineer/painter/architect/sculptor said "Art is never finished, only abandoned". It is the same with final year projects. What matters is the quality of what is done. So pick a small canvas and paint a still life! > Thanks, I'll look some more and see if I can find more ideas. > (Trouble is, I already registered glendix.org ;)) Call whatever you build glendix. Most s/w projects have silly names. Not plan9 of course.
