×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Programming requires proper training, and not everyone is capable of
doing this well.
No matter how good the language(s) or tool(s), in the hands of the
untrained, it can even be dangerous.
CASE STUDY
When I was in college in the 1970s, my mother worked for a company that
had IBM EAM (electronic accounting machines) punched card equipment, the
kind you "programmed" with wires on a plug-board. This system ran their
business, reading punched cards, and printing invoices, printing checks,
and reports, etc., successfully, for a good many years. This was a "not
for profit" corporation so their margins were rather thin.
Then, along came a slick fellow who sold them on the idea that they
needed to "modernize" and sold them an IBM System/3 or System/32. He
also sold them his own "consulting services" and claimed that he could
write all the new applications programs, equivalent to the old punch
card system, in RPG II.
When the time came to "go live" he had arranged for a salvage company to
come in and take away the old IBM EAM equipment (which was highly prized
because they contained valuable metals, such as gold-plated connectors,
etc.), on the very same day they "cut over" to the new system. (No
concept of running the new system "in parallel" with the old, and thus
being able to check the results against the original system, or in the
event that problems were found, they could have continued to use the old
system.)
It was soon discovered that the new system was sending out invoices to
people that should have been receiving checks, and vice versa, thus
ensuring that the company now had zero cash flow coming in, and rapidly
"pissing off" both their customers and the vendors who supplied the
merchandise. The fellow doing the programming kept promising to "fix"
the problem(s), but what ensued was a typical horror story of one
problem after another.
Within less than one year of the "cut-over" to this new system, this
company was "out of business" -- Chapter 7. No Chapter 11
reorganization -- game over!
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.