Shlomi Fish
Mon, 06 Aug 2001 05:36:32 -0700
On Mon, 6 Aug 2001, guy keren wrote:
>
> On Sun, 5 Aug 2001, Shlomi Fish wrote:
>
> > Part of the reason I cannot estimate its time to completion is because I
> > don't know how many developers are going to work on it.
>
> assume only you work on it - make an estimation based on that - and try
> to be realistic, and include design time, and coding, and debugging, and
> bug fixing. then - triple the number (that's the usual factor i take when
> i need to estimate how long it'll take me to do something i haven't done
> before). give us the time in 'work days' units (net time).
>
I think I can make a better estimation as soon as I write a SPEC of the
simulator internals and behaviour. However, there are two things I'd like
to do first:
1. Read the book again to remember all the small details that I since
forgot. I remember the MAYBE in general lines, but I forgot some things
since then. However, since I got along well with the course, I think that
it should not take too long.
2. Talk with the supervising lecturer of the course (Dr. Michael Werner)
and ask him for his opinion, what he can do to assist us, etc.
Thus, I for the time postpone my suggestion to a time after I will
write the specification (and post it here) and talk to Dr. Werner.
> > But I can tell you in advance that the MAYBE simulator will not take too
> > much work.
>
> could you please be more specific?
>
I have the simulator in mind in general lines. But there maybe some
caveats in the physical structure of MAYBE, which I forgot, so I'd rather
consult the book before I delve into specifics.
> > And I believe we can split it into several steps, that each one
> > would be a mini-project of its own. That way, we can take some time to
> > procastinate with different projects.
> >
> > Would you agree to delay the final verdict until I rent the book and write
> > a more detailed description of the MAYBE's internals, as well as a
> > specification of the simulator's code, as I can plan it in advance?
>
> there's never a final verdict. eventually, if someone wants to do
> something - they just do it, not letting other people tell them its no
> good. so go ahead and make a specification. i assume it'll take a while -
> and meanwhile we could either wait, or start another small thing. there's
> no rush - MAYBE will still be there for us ;)
>
I say we start another small thing. That is, assuming the specification is
not ready by the time R2L has been finalized.
Regards,
Shlomi Fish
> --
> guy
>
> "For world domination - press 1,
> or dial 0, and please hold, for the creator." -- nob o. dy
>
----------------------------------------------------------------------
Shlomi Fish [EMAIL PROTECTED]
Home Page: http://t2.technion.ac.il/~shlomif/
Home E-mail: [EMAIL PROTECTED]
A more experienced programmer does not make less bugs. He just realizes
what went wrong more quickly.