View Single Post
Old 09-03-2007, 03:36 AM   #30
HarryT
eBook Enthusiast
HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.
 
HarryT's Avatar
 
Posts: 85,556
Karma: 93383099
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
Quote:
Originally Posted by LaughingVulcan View Post
It shouldn't matter much, according to my sister who has been working for some time as a Project Manager or Business Analyst in projects. Even if the technology is licensed out, the company doing the contracting or buying the license has the ability (and right and responsibility) to do a code walkthrough. (Assuming that the contract initiating the licensing is written correctly.)
I work in a company which produces software solutions for its customers, LV. Most of these involve licensing numerous 3rd party components and tools. Rarely, if ever, do these have source code available. One has to trust that things that you buy in do what their producers say that they do.

I'm not arguing, but the way, that Sony were legally responsible. I was asking who you blamed - Sony, or the company which produced the faulty software. To my mind, the blame lies clearly with the latter.
HarryT is offline   Reply With Quote