Date: Thu, 28 Mar 2024 09:08:11 +0000 (UTC) Message-ID: <2138331646.75.1711616891925@462808cf46fd> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_74_1042106122.1711616891925" ------=_Part_74_1042106122.1711616891925 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Don't lose sight of large scale reusability.
I've seen two different project approaches in regard to reusability.&nbs= p;
The OSID approach provides an interesting middle ground. Once an OSID Pr= ovider is developed and loadable, by definition it is reusable by any consu= mer of that OSID. OSID Consumers need not only be applications, but they ca= n be used by providers of other OSIDs whether or not it was the intent of t= he programmer.
OSIDs does not concern itself with micro-reusability. That is, making su= re everyone uses the same code for formatting a date or parsing an XML file= . OSIDs enable reusability of entire services.
This is not to say that code reusability outside the OSIDs is wrong. It'= s just that if one had to choose, reusability is far more beneficial for la= rge things. Fretting over small classes and utilities and ignoring the bigg= er picture provides little return. Programmers (like us) are too easily cau= ght up in saving the pennies and the OSIDs have been helpful in reaping the= pounds.