[Info-vax] HP wins Oracle Itanium case

[Richard B. Gilbert]

On 8/23/2012 3:10 AM, Howard S Shubs wrote:
> In article <fWcZr.7914$3d2.7300 at fx26.am4>, ChrisQ <meru at devnull.com>
> wrote:
>
>> By paying attention, expecting code to work first time, using safe
>> programming techniques and developing incrementally. (Well, you did
>> ask for that :-).
>
> Expecting code to work the first time strikes me as a complete
> contradiction to all my experience.
>
It happens from time to time.  Just don't count on it!

And don't break your arm while patting yourself on the back.  People
will remember that last two or three times were less than totally 
successful!

>
>> Of course you often need to debug code, but the point I was trying to
>> make was that the "debugger" should rarely be the first option. On
>> some sites, the debugger is the first thing to be fired up if a
>> program doesn't work, where 10 minutes analysing program behaviour
>> and sources is often far more productive...
>
> I think I see.  You're talking either about something I've never heard
> of, or you're talking about print statements.  I rarely see programs
> simple enough to do what you seem to be suggesting.
>
> You and Hoff seem to be coming from a realm of programming beyond what
> I've experienced.
>

Hoff, at least, has been around the track a few times.  I suspect that
he has made more than a few mistakes.  I've NEVER encountered anyone who
writes perfect code.