My dad was a Senior Software Engineer for Qwest (as Mountain Bell and US West) for 30 years. My wife is an embedded software engineer working on the very systems you're talking about. And her dad was an EE who worked for HP for 17 years designing integrated circuits.tunnelcat wrote:I'm married to an electrical engineer who worked for Hewlett Packard for 30 years
Different companies have different cultures and expectations. Those companies also change over time; "normal" practices in 1974 are different from current practices, as software development has matured a great deal in that time period. And of course the type of system they're developing matters; the level of checking that goes into a chip in a $10 toaster is different from the checking that goes into a $150 million fighter jet.
Good programmers do this piece by piece anyway; it's called "refactoring". Write it, get it to work, and then throw it out and rewrite it now that you know how to do it. Eliminates tons of bugs.Sometimes the entire code for a product was tossed out and redone!
Of course, it's a lot more expensive if you build up a bunch of bad software before you fix it.
Of course. That's the whole point of "Software Engineering", as compared to merely programming.you can't test in quality control, you really have to design it in if you want reliability
http://web.engr.oregonstate.edu/~cscaff ... _F09.shtmlit appears that software engineering is a totally different animal.... I couldn't find this type of engineering course at OSU's engineering school.
http://beaversource.oregonstate.edu/soc ... fall-2009/
SE has been around for a very long time, and it has become more common to see full-fledged degrees with that title instead of just one or two courses in a more generic CS program.