Rogue Code

One of the greatest challenges you will face with your Web Design is the challenge of rogue coding. A couple of days ago I was side-tracked by a missing ( ” ) within my code that had me scratching my head for most of the day. The entire site looked as if a 3 year old had designed it.

Usually, when you have rogue code that works it’s way into your Website, you will surely detect the issue or problem right away, as it is usually localized. However, when you are dealing with multiple layers of coding the challenges compound.

Rarely do I ever have an issue with rogue code if I am designing a Website from scratch. It’s when I have a Website design that is based on WordPress or similar CMS, where I have not only the “CMS” to deal with, but also a “Premium Theme” that I am using in conjunction with the CMS, and don’t forget the plug-ins that can and will cause issues.

Once you have a Website built, you should be working from a stable platform, so when rogue code enters into the equation, you can spot it pretty quickly.

The real challenge to rogue code is when you are designing a new Website. All of us at one time or another will borrow existing code from one design to insert into a new one. With such code you take your chances there will be no problems. Even if there is a problem, usually you note it pretty quickly. However, if you have those layers mentioned above, you can have real issues.

Sometimes code can work with your existing design and once you upgrade to a new design, the change in code within the new template or theme can conflict with your existing code that was working fine just moments earlier. Leaving you to wonder exactly where the conflict lies.

Experience has shown me that most of the problems lie with old code you were using that is no longer effective with your new design. If you look to your old code first, you will usually find your issue. Once corrected, your new Website will look as if Monet design it!