NOT MY FATHER'S ITERATION...
When developing software (or deliverables in general) ... it is a good practice to give your finished product an identifier distinguishing it from other like products (or even different variations of the same product).
Developers use different version identification schemes e.g. date-and-time-stamps, arbitrary numbers, code names or a mixture of the aforementioned. The most common among version control numbering schemes is the 0.0.0(.000)? scheme which is broken-down as follows:
The version number 0.0.0 could be (is usually) interpreted as version.edition.iteration, whereas the version number 0.0.0.000 would be version.edition.iteration.build having the build identifier correspond to the number of times the code has been compiled against said version of the code.
If a person is a product of his/her environment, .. more specifically if a person is a derived result of some original (parents, grandparents, etc), that doesn't necessarily make the person a new version, ... a 2.0.
I suppose what version you are depends on how much you deviate from the original version.
What version are you?