Was FORTRAN buggy 4327

That's my point. These can be impossible to fix because the new circuitry cannot be modeled into the code even though a human can fix it by stringing a wire from here to there.

But none of those tests that were developed for the software bugs can verify the hardware works.

I understand that current design processes require software and hardware development to be concurrent due to time-to-field presures which are getting shorter and shorter every year. The biz is quickly approaching the other extreme of the saying, "Ship every day or never ship" w.r.t. a working product. You should note that, as the limit of shipping every day is approached, the event of never shipping becomes more likely.

I understand. It's also looking like more and more valuable developer time is spent on tests rather than the real code.

These kinds of things are design flaws. These should be learned and the knowledge of what not to do applied to the next iteration of the gear. If you keep coding around it, nobody in hardware is going spend any time doing a real fix because it's not a problem they own.

I wonder if this schism is because the hardware and software biz have been divorced; the same capitalistic enbreasty is no longer responsible for both.

BAH