Today’s topic will be the importance of having two environments, one to develop your code in, and one to release into the public. Sometimes it is simply easier to edit, run, and test it in the live environment, but when your code deals with data, this becomes more problematic. Imagine some code that insert data into the database whenever you run it, if you run it in the dev environment, it’s really no big deal, but if you run it in the live environment, it might cause database pollution. Although your code should account for that case anyways, but it’s hard to say that during your “updates” you wouldn’t accident code it so that it starts inserting a bunch of meaningless data into your database. Having two environments will allow you to code and test in whichever way you want without having to worry about the consequences.