Building fault tolerant systems is a whole field, you are going to need to do a lot of study. It certainly touches on development methodologies such as XP, practices such as well-defined requirements and unit testing, use redundant hardware and power, use watchdog processes and well-defined error modes (with a catch-all well-defined way of crashing that won't kill your system) at all times, and also hire professionals. You still aren't going to be able to build something for aviation or a power plant with that though. For that you are going to need to make another quantum leap. It costs a lot of money and painstaking attention to make things that good. You might consider studying embedded device development paradigms too.
You may get some good responses here but I also recommend going to slashdot.org, where this sort of thing has been asked lots of time in the past (search for it). Or if you can't find it, post an Ask Slashdot. You will get a lot of replies.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.