> Many new programs I still come across have no output when they > work OR fail... Mainly I think because some people just assume why > wouldn't it work... Maybe they need more experience with badly behaved > software before we let them program in the real world perhaps :)
Perhaps people have *too much* experience with badly behaved software (Linux is bad enough, don't get me started on ffmpeg, web browsers, xpdf, or virus server...) and they think bugs are normal and acceptable. > (Or > it could just be a new thing... At uni i always had it drummed into me > about checking returns codes & reporting errors... You lost marks if > you didn't adhere to the rules... I think many programmers today just > don't have that background... These days it isn't safe to assume that programmers have been to uni. I read somewhere that Netscape hired a 14 year old. I wonder if they still show that film of the bridge falling down? Everyone's first job should be on a project where failures can result in death, and thus learn about concepts like reliability, testing, etc. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
