Re:Why does software cost so much?
by tabtab on Wednesday April 18, 2018 @12:45PM
(#16868829)
The buy-versus-build decision is not clear cut. Pre-packaged solutions often have a lot of "buttons" and layers that are distractions and/or extra steps that are not otherwise needed by a particular customer, and thus slow things down.
For example, a given org I once worked for had a 1-to-1 relationship between subscription user and payer (bill-to). But the pre-packaged software implemented it as a many-to-many relationship to be more flexible for different shops. One can use this to emulate a 1-to-1, but it's more layers, screens, and data tables than a dedicated 1-to-1 design. (My job was to build reports based on those data tables.)
Good home-grown software beats bad purchased software, and good purchased software beats bad home-grown software.
Re:Why does software cost so much?
by tabtab on Wednesday April 18, 2018 @01:17PM
(#16869092)
My point was that neither type is inherently better just by being a member of that type. The devil is in the details and both can be good or bad for a given organization or product need.
For example, a given org I once worked for had a 1-to-1 relationship between subscription user and payer (bill-to). But the pre-packaged software implemented it as a many-to-many relationship to be more flexible for different shops. One can use this to emulate a 1-to-1, but it's more layers, screens, and data tables than a dedicated 1-to-1 design. (My job was to build reports based on those data tables.)
Good home-grown software beats bad purchased software, and good purchased software beats bad home-grown software.