If you have a media platform for several companies and needed to make a quick change throughout the network of users you might wonder “how can I change the code on my end without touching the client’s code.” This has been an issue that has popped up in my career several times, and the easiest solution that I have come up with has been the use of iframes, or something similar.

With large companies, there is a large array of different reasons why things would need to be changed fluidly. This includes everything from changing of branding, to added functionality. There’s always a reasons to leave things open for a just in case scenario. This is why as a programmer, we always try to allow for ease of extensible coding and upgrades.

Several years back, coders used to load in various documents into a single holder, so why stop the trend? The one greatest reason for using iframes now is the fact that they’re backwards compatible and work with various other platforms without much trouble. Some people assumed that the use of frames was considered bad practice, until the advent of iframes.

Now I’m not saying go crazy with iframes, but do use them when you feel that a particular technology or project might change, especially if it’s not on your server. It makes for things to be much easier to work with if things were to change years down the line, without even having to touch the client’s code.