🚀 go-pugleaf

In sci.electronics, johnh@macadam.mpce.mq.edu.au (John Haddy) writes:

>I suspect that the local news feed chewed up my last attempt to post this. If it
>didn't then please forgive the repeat post!
>If you've seen this before, I promise that this will be the last time! I truly
>expected that the the topic would arouse at least _some_ interest, however I've
>only had one reply (from nearby), leading me to suspect that the original post
>did't get very far.

I saw the original post, but didn't respond because of the difficulty of
answering the question.  You essentially ask, "how long will it take to
build a project that takes longer than a week or so to build?"  My flip
answer is, of course, longer than a week or so.  The problem of scheduling
is always a difficult one, and it's not something that can be determined
simply, or usually with much accuracy at all.  Projects that I have worked on 
take anywhere from a few hours to years.  Clearly, your question excludes
the "trivial" tasks, but the range is still huge.  So the question is
almost impossible to answer in the general terms in which you're asking it.
I think it might be possible for people reading this group to estimate
how long it might have taken for them to do something if given more details
than you've given.  Perhaps if you would give more details of the projects
in question, without giving any expected or realized times, someone might
have a chance of estimating it.  Frankly, though, it sounds like your
organization is in need of better methods of evaluating employee's
performance.
		 - Jim