Copying vs stealing: what separates them in design
Someone on your team lifts a Dribbble shot wholesale into the actual product, or points an AI tool at a competitor's onboarding flow and asks it to build the same thing, and when you push back, you get the line. Good artists copy, great artists steal. It ends the conversation. It shouldn't, because the person who coined it meant something closer to the opposite of what it's being used for here.
Where the quote actually comes from
Steve Jobs credited it to Picasso in a 1996 PBS interview about the Macintosh's debt to Xerox PARC, and that is the version everyone repeats. Quote Investigator's archival research traces the real lineage: critic W. H. Davenport Adams made the original distinction about poets in 1892, and T. S. Eliot restated it in 1920 with the words reversed, immature poets imitate, mature poets steal, judged entirely by what the poet does with the borrowed material afterward.
The line was coined to condemn lifting something with minimal change, not to excuse it. A bad poet leaves the borrowed material sitting there, recognisable. A good one melts it down and rebuilds something that wasn't there before. That is the actual test, and it holds up better than the slogan does.
The test underneath the slogan
Across design, engineering, and law, the same distinction keeps reappearing under different names: did you reproduce the surface, or did you extract the underlying mechanism and rebuild it inside something new. Reproducing the surface produces a duplicate. Extracting the mechanism produces a descendant, something that has to stand on its own once the resemblance to the source is gone.
This matters more than a definitional quibble, because the two paths carry completely different consequences, both creative and legal, and mixing them up is expensive.
When a platform does the copying at scale
A third-party Mac utility called Watson, built by Karelia Software, shipped in November 2001. Nine months later Apple released Sherlock 3 with Mac OS X 10.2, carrying features that closely mirrored it. Apple's position was that this was the natural evolution of its own product. Watson's side said the features had been taken without permission, compensation or attribution. Karelia stopped developing the original version within two years and gave the last build away.
The episode is where "Sherlocked" comes from as a verb: a platform owner absorbing a smaller product's differentiating feature directly into the operating system, using structural advantages, deeper system access, zero distribution friction, that no independent developer can match.
It is legal. Apple was not reproducing Watson's code, only its feature concept at the OS level. It still functions as the bad version of the pattern, because nothing about the feature was transformed. It was relocated, with more resources behind it, to somewhere the original creator could not follow.
When copying becomes a courtroom question
Design has its own formal machinery for the same distinction, and it has real teeth. In Apple v. Samsung, Apple sued over design patents covering the black rectangular face, rounded corners, and grid-of-icons home screen, the look, not the underlying engineering. In May 2018, after a Supreme Court ruling on how design-patent damages should be calculated and a retrial, a California jury awarded Apple roughly $539 million.
| What's protected | Legal tool | Blocks |
|---|---|---|
| The exact code or image | Copyright | Reproducing the expression itself |
| How something works | Utility patent | Anyone making or selling the invention, for a fixed term |
| A product's visual design | Design patent / trade dress | Copying the specific ornamental look |
| A brand identifier | Trademark | Confusingly similar branding |
None of these protect an idea or a function. That gap is exactly where the legitimate version of stealing lives.
The engineering version, done on purpose
Software engineering has a formal, legally sanctioned way of doing this cleanly: clean-room reverse engineering. When IBM's PC BIOS was copyrighted in 1981, Phoenix Technologies built a functionally identical replacement by having one team write a plain-language spec of exactly what the BIOS did, then handing that spec to a second team that had never seen IBM's actual code, which implemented it from scratch. IBM never successfully sued.
That is Eliot's test turned into case law. The specification, the behaviour, was permitted to be copied. The implementation, the specific expression, had to be independently rebuilt. TRIZ, the engineering methodology Genrich Altshuller built by manually working through patents on the order of hundreds of thousands, formalises the same move for invention generally: extract the underlying contradiction, not the specific implementation, then solve it with one of roughly 40 recurring principles that keep resolving it across unrelated fields.
Nature doesn't hold a design patent
Biomimicry is the version of this with the ethical tension removed entirely, which is useful precisely because it isolates what people actually object to elsewhere. Engineer Eiji Nakatsu redesigned the Shinkansen bullet train's nose after a kingfisher's beak to fix a sonic boom on tunnel exit, and the redesigned train ran roughly 10% faster while using roughly 15% less electricity. Nobody frames that as theft, because there is no displaced competitor and no lost market on the other end. What's left, once you remove the victim, is the actual mechanism people object to in every other case in this post: not the act of borrowing, but what borrowing does to whoever's original position gets displaced by it.
The line the AI frontier just redrew twice
Two 2026 rulings put fresh, formal weight on exactly this distinction, and both concern a company whose model you may be shipping design work through right now. On July 20, 2026, a federal court granted final approval to a $1.5 billion settlement in Bartz v. Anthropic, after the court had already found that training on pirated books specifically was not fair use, separate from the broader, more favourable ruling on training on legally acquired text. On March 2, 2026, the US Supreme Court declined to review Thaler v. Perlmutter, leaving standing the rule that a work with no human author cannot be copyrighted at all.
Read together, both rulings are the copy-versus-steal test applied to a new medium: one punishes reproducing the source material itself without a license, the other refuses to grant protection to output with no transformation step a human actually performed. Neither case is about design specifically. Both are the same argument this whole post has been making, decided in a courtroom instead of a critique.
The check, run before you ship the borrowed thing
Before a reference, a competitor's flow, or an AI-generated pattern goes into production, spend five minutes on one question: if the source disappeared tomorrow, would this still hold together on its own terms, or would it visibly need the thing it came from to make sense. If it needs the source to make sense, it was copied. If it doesn't, you actually stole it, and Eliot would have approved.