On December 15, Richard Erlacher wrote:
> Well, perhaps the reason for all the meetings and other work you find
> uninteresting is that it's necessary to arrive at a firm specification for what
> you have to build before you go off and build it. Since the coding, compiling,
> and debugging only represent about 5% of the task, the bulk of the work has to
> happen sometime, and that's what the "other" stuff is.
Some documentation and speficiation has to happen, sure. But most
of the industry seems to have lost sight of the fact that these are
*overhead tasks* that are secondary to the job of *building
something*. It gives suits a reason to take home a paycheck...they
can shuffle paperwork and Powerpoint bullshit all they want; it
rarely contributes to the finish product.
It's not an issue of my finding it "uninteresting"...I write code.
That's what I do best. If I'm doing something other than writing
code, I'm likely wasting my time...or worse, someone else's...because
if I'm not writing code I'm probaby doing something I'm not
particularly good at.
I'm not trying to be argumentative here...though it may sound that
way, please don't take it as such.
Again I will qualify my statements as pertaining to sub-million-line
development projects, not huge multi-million line behemoths.
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
Received on Sat Dec 15 2001 - 23:25:39 GMT