When a Hidden Easter Egg Almost Cost an Engineer His Job at Apple

Background

In 1995 John Calhoun, a former independent Mac game developer, joined Apple as a QuickDraw GX graphics engineer. After the QuickDraw GX project failed, he was moved to the ColorSync team to port the system Color Picker from Motorola 68K to PowerPC.

Technical Task: Color Picker Migration

The Color Picker consisted of two modules:

HSL picker – originally written in 68K assembly for real‑time rendering of the hue‑saturation‑lightness wheel.

RGB picker – standard three‑primary‑color interface.

Because the assembly code could not run on PowerPC, Calhoun rewrote the HSL logic in C. This required understanding the original callback architecture and reproducing the high‑performance rendering on the new architecture.

Additional Features Added

HSV picker – Calhoun preferred the hue‑saturation‑value model for artistic work and implemented a full HSV selector.

HTML (hex) picker – displayed colors as six‑digit hexadecimal strings (e.g., #FFCC33) for web designers.

Crayon palette – a 60‑color “crayon” set with visual aging effects; colors regenerated each Christmas.

Easter Egg Incident

While adding resource names, Calhoun embedded a short excerpt from T.S. Eliot’s poem “The Love Song of J. Alfred Prufrock” as hidden strings. He assumed the text was public‑domain and that the brief quotation qualified as fair use.

Apple’s build‑time checks flagged the strings as a potential copyright violation. The discovery triggered a formal meeting with his manager and a senior executive. Apple ordered the destruction of a batch of OS installation discs that contained the poem.

Calhoun apologized, was reprimanded, but ultimately retained his position after promising not to repeat the mistake.

Lessons and Recommendations

Understand and follow corporate IP and quality‑assurance policies before adding undocumented resources.

Perform a legal review of any third‑party text, images, or trademarks used in code or resources.

When working on legacy code migration, document all changes and seek peer review, especially when introducing new modules.

Consider the risk/benefit trade‑off of non‑functional Easter eggs: they can add personality but may expose the project to legal or compliance issues.