Quote
Since when in the IT industry do you edit a live system???
As a Dutch person I will not be liked, but I think the average Dutch person has a very bad habit of immediately using something. Only when things go wrong do we look up and read the supplied manual to understand how we could have worked better.
We can learn how to build a beautiful house with a hammer, but there are people who use the same hammer to smash into someone else's brain.
Just as it is too simplistic to see a hammer as a murder weapon only, it is also too simplistic to say that SitePad does not distinguish between a production and a development environment.
Firstly, you can make an adjustment in a web page of the live environment without saving it. You can then test the modified version next to the existing production environment. If the adjustment is not satisfactory, you simply throw away the changed page without affecting the production environment.
If you are happy with the adaptation, but you don't want to put it into production yet, you can mark it as personal or declare it as a draft version.
And if you save the modified version, just save the definitions in a database without the modification(s) being implemented in the production environment.
Then of course you also have the option to save the definitions of a web page stored in the database with a backup / restore action or to restore them to an earlier version.
Yes, then as a last step you can update the published web page by making the changes in the live environment.
Of course, without having read the manual and without having used the smart options, as a Dutch person, I can implement the changes directly in the live environment. Not preferred, but if you get it right right away without making mistakes, it's a quick method.
So the answer to your question: "Since when in the IT industry do you edit a live system???" is therefore:
Quote
Since the Dutch immediately started working without a manual
(sorry fellow countrymen).