RESHAPING - index

Wherein we define the term: Reshaping.

        Simplicity is the ultimate sophistication.
          -- Leonardo da Vinci

Many times — as many people do — when we starting writing code we go through an iterative process of re-design. Every once in a while, after code becomes stable, we re-write the code.

As in introduction of what we mean, see MYSQL about our MySQL code module.

This is code reduction taken to it's limit. We developed the mysqli version over a few months — i.e. an iterative process of starting with a "proof of concept" (a "quick hack" if you will), not caring too much about efficiency or duplication etc., just to get things working satisfactorily.

Once stable, we revisited it with an eye toward code reduction; consolidating duplicate code into sub-functions for example. Then, once stable again, we looked at code efficiency. (Others will have their own steps to improvement.)

Each iteration came when "their time was due", when something "became apparent", and not on a fixed schedule. We write code with the idea in mind that everything and anything can change at some point if we can improve the code in some manner. But we tried not to have to change it all at once — only a little bit at a time when it seemed right to do so.

We are claiming the term "Re-Shaping" for this process (not to say that no one else works like this or that we have "first use"). The code is like a blob of clay and we mould it into something cool looking over time.

Notes

1. It's not always a forward process as there have been times when a proposed change had to be undone.