Skip to main content

Backup The Template, When Making Changes

If you've ever done programming - including updating existing code (generally made by another person, who you grow to hate) - you know of the value of backups.

Any time you improve or repair existing code, there is always the possibility of making mistakes. Code is written by people - and people make mistakes. Sometimes, the mistake may be in the code, as originally created (and used for months, until you touched it). Other times you make one mistake on your own, and the whole thing crashes.

Experienced programmers know that making mistakes is part of programming. When you make a mistake, be prepared to recover from - and learn from - the mistake. This is true, when making template changes, in your blog.

Any time you change the template in the blog, you are doing programming.

Code updates require technique.

Experienced programmers know the proper technique for making changes to existing code.
  1. Backup the code.
  2. Make the changes.
  3. Test the changes.
  4. If problems are found,
    • Restore from Step #1.
    • Identify the mistake.
    • Return to Step #2.
  5. If no problems are found, backup the code, again.
  6. Log the change, with date, time, and description of change.
  7. If mistakes are found later, consult Step #6, then return to Step #4.
This is especially a valuable policy, if you are making changes to the comment / posts section of the template - which Blogger Engineering may update, any time, without warning.

Only one step is absolutely essential.

You can leave out any step, in the procedure above (excepting #2) - and you may get the job done. You can do Steps #2 and #3 carefully, and create check lists and check points, and have code reviews. If you never make mistakes, Steps #1 and #5 are not really needed. Nor is #3 (but don't tell your boss!).

But my experience is that if you do Steps #1 and #5, consistently, you will be able to do Steps #2 and #3 more confidently - and you will make less mistakes because you are less stressed.

The one time that you omit any step, you will learn to not take shortcuts.

And the one time that you omit Steps #1 and #5 - and have to re build the whole code set, by hand, from the ground up, you will know that Steps #1 and #5 are not optional. Nor is Step #6, which helps you identify which backup to go beck to, when mistakes are discovered.

Backup the template - before and after making changes. You'll have less stress, and more time for working on blog content.

Comments

Popular posts from this blog

Custom Domain Migration - Managing The Traffic

Your blog depends upon traffic for its success.

Anything that affects the traffic to your blog, such as any change in the URL, affects the success of your blog. Publishing the blog to a custom domain, like renaming the blog, will affect traffic to your blog. The effects of the change will vary from blog to blog, because of the different traffic to every different blog.Followers. People who find your blog because of recommendations by other people.Search engines. Robotic processes which methodically surf your blog, and provide dynamic indexing to people who search for information.Subscribers. People who read your content from their newsfeed reader, such as the dashboard Reading List.Viewers. People who read your content from their browser.No two blogs are the same - and no two blogs will have the same combinations of traffic sources.

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.