That's been my experience, too. What I find especially telling is that my local Barnes and Noble has two section: one, labelled "Programming" has mostly books about, well, programming; another, labelled "Software Engineering" has mostly books about process.
I agree with Kevin that software engineering SHOULD NOT be any different from other types of engineering, but unfortunately, what we call software engineering is often more of an approach to management than anything else. Now, don't get me wrong: I believe management is important, but there is a void thaqt is not being filled here, and that is the application of technological, scientific and mathematical principles and techniques to the creation of software; in a word: engineering. --- Larry Andreassen <[EMAIL PROTECTED]> wrote: > Comparing small and large team projects I've been involved with... > Small teams... "Do the work..." > Large teams... "Do the process..." > By process I mean a pre-defined set of steps, documents and stages. > And, > often these stages do not fit naturally with the work. === Gregory Woodhouse <[EMAIL PROTECTED]> "Without the requirement of mathematical aesthetics a great many discoveries would not have been made." -- Albert Einstein ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
