In article <[log in to unmask]>, Therm-O-Link
<[log in to unmask]> writes:

>On Thu, 22 Jan 1998 23:02:55 GMT, HDraexler <[log in to unmask]> writes:
>
>>I just calculated ... in the last 15 years I spent 1872 hours,  just
>searching
>>for compiler errors! But now there is VSPF ...
>
>Let's see now, 1872 / 15 =3D 124.8 hours per year, divided by 52 =
>
>(weeks in a year) =3D 2.4 hours per week, divided by 5 (days in =
>
>a week) =3D .48 hours per day.  If you work an 8 hour day, then =
>
>I assume you spent the remaining 7.52 hours either creating =
>
>compiler errors or fixing compiler errors.  Not very productive, =
>
>are you?  It's a good thing you don't work for me, you would have =
>
>been fire a long time ago. :-)
>
>Jim Phillips                            Manager of Information Systems
>Voice: (915) 860-9933                   Therm-O-Link of Texas, Inc.
>  Fax: (915) 860-9936                   1295 Henry Brennan
>Email: [log in to unmask]       El Paso, Texas   79936


If your programmers do need more than 6 % of their time just for
searching, finding and fixing compiler errors - oh man, you should fire them
soon and get some programmers who are worth the money. :-)