> >With all of the complaints seen in the past ("Where's the NCR2 demo?"
> >"Has GP2 been released yet?", etc.), why don't the programmers over
> >estimate the release dates of their software? As engineers know, you
> >should always have a "safety factor" in case something goes wrong. So
> >why not just add 2 weeks to your estimated release date. That way, when
> >the product is not complete by the estimated date, there won't be as many
> >complaints. The programmers will not be in such a rush to complete the
> >product and some of the bugs might get themselves worked out. If the
> >programmers actually finish on time, then great! Release it early.
> >Just my opinion
> >Randy Johnson
Actually, EVERY release date given to us voltures here at r.a.s,
is an OVERESTIMATED date. Just sometimes bugs are found in the programs,
and it slips PAST the date, and then the designers try NOT to
overestimate again (that'll get people angry), and 1 release date slips
by, then another, then another and before you know it the program is
vaporware (BC3K springs to mind, the 7 YEARS overestimated release date
was supposed to be september. Well, its not anymore)
--
Macarena, hiphop,rap,soul,rythem,disco,pop,dance,trance,rave,techno)
/ \
--------------------------------All SUCK--------------------------
Smashing pumpkins RULE!
Roey