Ah…found it. Someone posted a humorous list internally that included this
section:
HARDWARE/SOFTWARE PARADIGM:
A program is a device to show up hardware faults; hardware is the
equipment used to show up software faults.
A bad workman blames his tools; a Systems Analyst chooses from: the
hardware, the software, the manual, the operating system, the interface,
the peripherals, the ambient temperature, the night shift, the day
shift, operators, programmers, BT, Mercury, the customer’s
specification, fluctuations in the power supply, those Taiwan chips,
that last pint with the supplier’s sales engineer
cheers,
Kris
“Kris Warkentin” <kewarken@qnx.com> wrote in message
news:apos8a$2vt$1@nntp.qnx.com…
I read recently somewhere that software is a tool to find defects in
hardware and that hardware is a device to expose weaknesses in software.
Kris
“Rennie Allen” <> rallen@csical.com> > wrote in message
news:> 3DBF8FA6.3040401@csical.com> …
Kris Warkentin wrote:
Just because they SAY they’re going to do their next project with some
OS,
doesn’t mean that they will. Many of them will not have done enough
in-depth evaluation to really know if it’s doable or they’ll just try
anyway, fail, and then go off crying to the nearest RTOS vendor.
The scary thing about Linux calling itself an RTOS is that
when people fail (and they will), some portion of them will
not go running off crying to an RTOS vendor, but will instead
conclude that commercial RTOS’s are a boondoggle, concede to
the EE’s, and write to the metal (I have seen this happen).
ps: no offense intended toward EE’s, but you know the type
to which I refer (the hardware engineer that views
software as some sort of infection that his hardware
develops after he releases it into the wild).
And