Shaqeled

This is a fresh new term used in Southern California for the occurrence of development environments gone awry. When developing software using separate development and production servers, it is not rare to see bugs seen in one environment that do not exist in the other environment. When you are using your development environment and all of a sudden your program acts as if it is in production you have been shaqeled. The cause is unknown at this point, but the effect is often seen.

This phenomenon is most often witnessed in IFrames, while the rest of The Browser window will remain unaffected. Currently, it is an issue that is solely associated with internet explorer. Other browsers will react fine to the same program that gets shaqeled in IE. Interestingly, if you have the balls to put that code on a production environment, it will work more often than not.

While the cause of Shaqeling remains a mystery to even the brightest minds in software development, the origin is well defined. The first time a programmer was Shaqeled was in downtown San Diego. A user was supposed to be signed in as dell1gogo@gmail.com (dev environment) however some how he got logged in as Shaqel (Production environment). This user did not even exist in development.

There is a large reward out for anyone who can figure out why the phenomenon known as 'Shaqeling' occurs. The currency may only be respect, but it is [...] worth it!

Note: There is talk of a similar phenomenon known as inverse-shaqeling where the opposite occurs. Some how production environment iframes hit development databases. This has not been formally proven yet, however it should be noted that it is a possible issue.