On April 14, 1561, the citizens of Nuremberg witnessed something extraordinary. According to contemporary accounts, the morning sky filled with what appeared to be cylinders, spheres, and crosses engaged in an epic aerial battle. The local broadsheet described "a very frightful spectacle" where these objects "fought among themselves" before many fell to earth "as if they all burned."
Whether this was an unusual aurora, atmospheric phenomenon, or something else entirely, what fascinates me as a technologist isn't the mystery itself—it's how the witnesses interpreted what they saw. They described it in terms they understood: a battle, with familiar shapes fighting in the heavens. They took something completely outside their experience and made sense of it using their existing mental models.
This is exactly what happens when we launch new software or introduce innovative features to our users. We might see elegant code and revolutionary functionality, but our users see it through the lens of their existing experience. The Nuremberg witnesses didn't have the vocabulary for meteorological phenomena, just as our users might not immediately grasp the genius of our latest API design. The lesson? Don't just build something amazing—build something that translates amazement into understanding. Sometimes the most innovative thing we can do is present the extraordinary in terms that feel surprisingly familiar.