Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] The Airplane Example (was Re: [xml-dev] Streaming XML)

From: Bob Foster <bob@------.--->
To: Benjamin Franz <snowhare@-------.--->
Date: 1/1/2005 12:28:00 AM
Benjamin Franz wrote:
> Hmmm...Hard one. I would say yes. Becoming a licensed professional 
> engineer requires more than graduating with a engineering degree. It 
> also required some (typically 4) years of experience before you are 
> eligible for licensing and a grueling examination. The medical 
> profession also uses a degree/testing/internship system. As does the 
> legal profession.
> 
> The pattern is pretty standard in the professions:
> education + testing/board + internship -> licensing

Actually, it's:

education + internship + testing/board -> licensing

But you knew that.

> Here is an interesting diagram from the National Society of Professional 
> Engineers:
> 
>  http://www.nspe.org/etweb/1!-00-2000_Licensure_Model_Law.asp

That is interesting. In that model, a CS MS would be worth a year's 
experience. Very funny.

The problem with licensing is garbage in, garbage out. Where does the 
prospective software engineer get that professional education? 
(Stanford? Cisco State?) Where does he/she intern? (Do they all go to 
work for Lockheed? Do some work for ThoughtWorks?) How do you establish 
competence when there are so few generally recognized good practices and 
the ones that exist have so little justification? (Prophets spring up; 
they attract followers. This is engineering?) Seems like a heckuva 
bootstrap problem to me.

I personally think the only way to significantly improve programming is 
for almost all humans to stop doing it.

Happy New Year.

Bob Foster


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent