On 12/08/2014 10:09 PM, Carlos E. R. wrote:
On 2014-12-09 03:25, Anton Aylward wrote:
He made about $100 the first week, about $50 the second and settled down to about $10 each week for the rest of the project.
:-)
I read a report time ago about a company, British, I think, that guaranteed perfect code. For small but critical components of larger projects (not guis or applications). It takes them a year and a half designing, before they even wrote a single line of code. Then much less "coding". I think that they managed what they claimed, and charged a terrible amount for it. I think that if the client finds a bug there are penalties. And apparently there are not.
Yes, this type of "Code? Why that's the last thing I'll do" approach to ultra reliable software engineering is not unknown among those willing to pay for it. Its why some dedicated aerospace projects such as the NASA deep space probes use this technique. You'll also not the "small". Keeping it small limits the number of interactions. There are a few very fundamental principles of ultra reliable software design and keeping "interfaces" and "surfaces" small is among them. Applying this to other projects need not be expensive; its the learning curve that is expensive. Some military aerospace projects have used this but on the whole too many military items use OTS. We've all seen the reports of the US navy ship that ran Windows and was dead in the water when it crashed. I've tried googling but can't find it .... Perhaps you recall the cartoon of the over-the-shoulder shot of pilot in a a plane cockpit approaching the runway and the display has the windows error message "restart, retry abort". No, that cannot be allowed to happen. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org