There are a few “bugs” you should be are aware of: At this time, our online designer works on most tablets and not on all smartphones and works best when used on an actual computer.
On Macintosh Safari or Chrome browsers: If you experience a delay upon uplaoding a high resolution image from your computer and the system seemingly stalls before getting to the next screen, wait for about 45 seconds before attempting to hit the refresh button. If you encounter a screen with the message “Processing…”, please log out and log back in and start over. Please stay tuned.
Please feel free to drop us a line if you encounter any other issues in need of our attention.We are working on making this site work for all platforms.
Some fun history facts on the word “bug” in software design
from Wikipedia.org
Etymology
Use of the term “bug” to describe inexplicable defects has been a part of engineering jargon for many decades and predates computers and computer software; it may have originally been used in hardware engineering to describe mechanical malfunctions. For instance, Thomas Edison wrote the following words in a letter to an associate in 1878:
It has been just so in all of my inventions. The first step is an intuition, and comes with a burst, then difficulties arise — this thing gives out and [it is] then that “Bugs” — as such little faults and difficulties are called — show themselves and months of intense watching, study and labor are requisite before commercial success or failure is certainly reached.[3]
The Middle English word bugge is the basis for the terms “bugbear” and “bugaboo”, terms used for a monster.[4] Baffle Ball, the first mechanical pinball game, was advertised as being “free of bugs” in 1931.[5] Problems with military gear during World War II were referred to as bugs (or glitches).[6] A page from the Harvard Mark II electromechanical computer’s log, featuring a dead moth that was removed from the device
The term “bug” was used in an account by computer pioneer Grace Hopper, who publicized the cause of a malfunction in an early electromechanical computer.[7] A typical version of the story is given by this quote:[8]
In 1946, when Hopper was released from active duty, she joined the Harvard Faculty at the Computation Laboratory where she continued her work on the Mark II and Mark III. Operators traced an error in the Mark II to a moth trapped in a relay, coining the term bug. This bug was carefully removed and taped to the log book. Stemming from the first bug, today we call errors or glitches in a program a bug.
Hopper was not actually the one who found the insect, as she readily acknowledged. The date in the log book was September 9, 1947,[9][10] although sometimes erroneously reported as 1945.[11] The operators who did find it, including William “Bill” Burke, later of the Naval Weapons Laboratory, Dahlgren, Virginia,[12] were familiar with the engineering term and, amused, kept the insect with the notation “First actual case of bug being found.” Hopper loved to recount the story.[13] This log book, complete with attached moth, is part of the collection of the Smithsonian National Museum of American History.[10]
The related term “debug” also appears to predate its usage in computing: the Oxford English Dictionary’s etymology of the word contains an attestation from 1945, in the context of aircraft engines.[14] History
The concept that software might contain errors dates back to Ada Lovelace’s 1843 notes on the analytical engine, in which she speaks of the possibility of program “cards” for Charles Babbage’s analytical engine being erroneous:
… an analysing process must equally have been performed in order to furnish the Analytical Engine with the necessary operative data; and that herein may also lie a possible source of error. Granted that the actual mechanism is unerring in its processes, the cards may give it wrong orders.