Re: Software Engineering is not a hoax...

[Scott Stanchfield <scotts@metaware.com>]

Dean Runzel wrote:
> 
> I'm picking up this thread very late but I'd like to join in with a
> few simple ideas:
> 
> 1) Engineering is basically the application of techniques to solve
>    problems. One of my EE instructors (long, long ago) said we would
>    be lucky to ever actually use something we learned in college
>    in a real world situation. Instead, he insisted that the school's
>    primary role was to teach problem solving techniques i.e. breaking
>    a problem down, combining techniques, etc.
An enlightened fellow, I must say...  That's the kind of teaching we
need!

RE the rest of your note: I guess the whole "engineering" issue depends
of the definition of engineering.

By your definitions, I would tend to agree that SW Engineering is a
"valid" term.  The problem is that by the same definition, one could
call a certain field of art "Painting Engineering."  (Applying
techniques to solve problems involving painted pictures.)

I think there's a "line" somewhere between art and science, albeit a
very fuzzy and very thick one.  They say that half the brain is
"logical" while the other half is "creative."  I get the feeling that
neither half is ever really "asleep."

SW Development (as I refer to it) involves several creative processes. 
But it also involves several logical processes as well.  It's a good
mix.

But like I said in an earlier post, I think the problem comes when
people characterize it like a field that clearly falls on the
"mechanical production" side of the line.  What I mean here is the
assembly-line analogy that "we have parts we just plop them together."
Personally I don't think SW development can ever become that.

And if it did I know I'd be looking for another line of work...

- Scott

-- 
Scott Stanchfield
MetaWare Incorporated
Santa Cruz, CA
(The opinions expressed herein are not necessarily those of MetaWare)