Go work for someone like Rockwell Collins doing avionics software. Mostly what they do is test, test, test, and at the end of a long day of testing, they test some more. I know, because some of my best buddies scored jobs there, and now they do Ada in front of green screens.
I suppose that's one way to make a living.
Proving programs correct most probably sucks for anything non-trivial. What are you going to prove? That it follows the specs? Broken as designed would devolve to "proven worthless". So it comes back to writing good specs. Good bedside material.
Finally, don't sell metaphors short ... metaphors are a well tested mechanism for transmitting knowledge between human beings.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.