Bridging the gaps in Software Engineering

re: Bridging the gaps in Software Engineering

Curt — Wed, 02 Mar 2005 22:55:00 GMT

re: "When was the last time a Software Engineer had to carry Errors and Admissions insurance?"

FYI, it's "Errors and Omissions" insurance. And yes, it's sometimes required in software consulting and contracting.

re: Bridging the gaps in Software Engineering

Jeremyk — Wed, 02 Mar 2005 23:01:00 GMT

Corrected Omissions... darn spell checker :)

re: Bridging the gaps in Software Engineering

Daniel Auger — Wed, 02 Mar 2005 23:10:00 GMT

Here is a great (albeit 10 years old) article on the state of "Software Engineering" versus other traditional types of engineering.

http://www.sce.carleton.ca/faculty/ajila/4106-5006/Prospect%20Eng%20Soft.pdf

re: Bridging the gaps in Software Engineering

Mike Gunderloy — Wed, 02 Mar 2005 23:24:00 GMT

Actually, it's quite routine for software engineers to carry E&O insurance. Anyone who subcontracts to Microsoft is required to carry it, for example.

But that minor nitpick shouldn't be allowed to obscure the larger point that there's a big difference between software engineering and the harder engineering fields in most cases.

re: Bridging the gaps in Software Engineering

jeremyk — Wed, 02 Mar 2005 23:35:00 GMT

So on the topic of "Errors and Omissions", my point was more so related to the ability to practice your profession. As a licensed P.E. by your state, you must carry E&O, either through your employer or personally. You can design a bridge for public use, but a PE must put their John Hancock on it, therefore accepting legal liability.

re: Bridging the gaps in Software Engineering

vincem — Thu, 03 Mar 2005 08:01:00 GMT

Cool article Daniel, thanks! It would be interesting to hear the authors opinion today.

re: Bridging the gaps in Software Engineering

Daniel Auger — Thu, 03 Mar 2005 19:44:00 GMT

Vince, I have been wondering the same thing. I think a lot of the things that have happened in the developer community over the past 10 years (Patterbs, Forums, Wiki, Blogs etc...) have filled in some of the gaps that were lacking for traditional reference material / knowledge transfer mechanisms.

re: Bridging the gaps in Software Engineering

Peter Johnson — Fri, 01 Apr 2005 13:17:00 GMT

Very cool article which every user should be made to read!! I think part of the problem is the majority of users who use software have no idea how it all works and can't think virtually. They seem to think you can do anything and it magically just happens and when it breaks it isn't their fault. Most people wouldn't take a tank across a bridge clearly marked with a 5ton limit but they would happily drop a 100mb attachment into Outlook and then scream at IT when it doesn't work. Experienced this numerous times. I think it's the very nature of PC's/software that causes this problem. I'm not sure that the principles that it operates on have been around long enough to sink into the collective conciousness of the world say the way driving a car has. regards from South Africa Peter Johnson

Desktop Computers » JeremyK’s [MSFT] WebLog : Bridging the gaps in Software Engineering

Tue, 18 Mar 2008 15:57:53 GMT

PingBack from http://desktopcomputerreviewsblog.info/jeremyks-msft-weblog-bridging-the-gaps-in-software-engineering/

JeremyK s MSFT WebLog Bridging the gaps in Software Engineering | low cost car insurance

Wed, 17 Jun 2009 07:38:09 GMT

PingBack from http://lowcostcarinsurances.info/story.php?id=2235

JeremyK s MSFT WebLog Bridging the gaps in Software Engineering | patio umbrella

JeremyK s MSFT WebLog Bridging the gaps in Software Engineering | patio umbrella — Thu, 18 Jun 2009 06:51:29 GMT

PingBack from http://patioumbrellasource.info/story.php?id=1358