The Quality of Code is not strained...

FOSSBazaar is no longer being updated. The information on this site is preserved for your convenience but may be out of date. Please visit Linux Foundation's Open Compliance Program for current information and activities.

Andrew Grant's picture

A proprietary vendor supplied us with their code and details of performance for one of our teams to integrate with our existing systems. No news there, happens every day across the enterprise. However, as the implementation scaled it exposed fatal flaws in the proprietary code when under load - bringing everything to a grinding halt.

As a consequence, we were obliged to rework the code for the vendor (having first pointed out all the flaws) – which entailed decompiling the Java, analysing and reworking it in order to get the system up and running again as well as additional improvements in the SQL queries. Because it was proprietary, there was no internal documentation available, no visibility of the code and no published schema to work with.

How much easier would this have been had the code been created as free and open source – then we could have had access to the full story with context – and it would have been quicker and easier – and the code would now be public domain and usable by everyone. Even then – had the code originally been written on the basis that it would have had peer review the question arises – would it have been allowed out containing the fatal flaws...?

Gadzooks, caveat emptor methinks.