"Dr. Soandso, do you believe, based on your experience, that such an action would constitute a flagrant abuse? Of a kind that is unprecedented? And such an action would damage the reputation of many, you say? And were such an action to take place it would cause harm to the industry for decades?"
The jury needn't be an expert to make sound judgements. Expert witnesses do actually need to socially regarded as experts, and lawyers on both sides of this adversarial system should do everything they can to undermine those experts who are not impartial. And if each player in that system does their job well a layman should certainly be able to make a reasonably founded decision.
How does the Jury tell two experts apart, while one says Yes and the other No?
The article is, literally, about this not working.
I've actually been in this exact situation as an expert witness. The defendant had written code in language "A", sold it, then wrote similar code in language "B". The question was whether code "B" had been written while looking at code "A".
The answer was yes, and I could prove it. Code often has a history that's apparent (e.g., you throw in an if statement to catch a weird input, and you add a comment like "fixing the wheelabrator-fry issue from december"). New code won't have the same history, and therefore should not have the same structure. If it does, the code must have been copied.
That's especially true if there are dated comments in the code.
What I wasn't asked was the economic value of the copying. Other experts handled that; I was just an expert in the two languages.
BTW: the final assessed value was much less than the cost of the trial. And I felt sorry for the defendant; most of the code had not been copied.
This seems a little weird--what if the author just remembers to, for example, make sure and handle those edge cases when starting again?
It would be nice if the answer could somehow always be a short expert witness testimony, but the reality seems to be that in some areas it's months or years of study.
In your example, you'd have to explain what source code is, what a graphics library is, methods of representing and comparing source code, and how the applicable laws are supposed to function. Sure, you could probably give them a vague impression in a short time, but not enough to decide something complex.