What ever happened to Tandem and NonStop OS 1994

Eric Chomko

Yeah, clearly. All I know about PERL is that it is "write-only". I also know that people who rely *heavily* on the RP approach to developing a product are doing that because they don't understand what they are doing at all.

You plan for failure. It will happen. There's no need to be afraid of failure if you are an engineer, that's part of the business. If it was easy any schmuck could build a safe 5 mile long single span bridge or develop a safe fly-by-wire system for a airliner.

I'll stick with break thank you. "Do not work" can be attributed to a deactivated perfect system, break means that the system is failing to function correctly and that is precisely the meaning I wanted.

SNIP

I have. I still think Rapid Prototyping is bad. It has a habit of being released to production, and when it breaks no one can figure out how it is *supposed* to work because the brutes who cobbled it together don't know either.

A good prototype is built to explore the problem space. Doing that often requires extra instrumentation and it almost inevitably runs in a padded cell type environment (because it ain't the full featured thing - so it can't survive in the real world).

You (and many contemporary methodology gurus) appear to be deliberately confusing production quality code and hacked up pooe.

Compare and contrast Clean-Room with RP for results...

Cheers, Rupert