Fig:1/**************************************************************************************
Author: Daniel "Loony" Haddad
Version: 1.0
Input:
THe Recursive Algorithm of Life takes as input Humans.
The “Humans” class has two main children: 1. Strivers
2. Simpletons
Both Strivers and Simpletons are created with the same allocation of bytes.
The only notable difference between the Strivers and the Simpletons or basically what sets them apart is only discovered upon running or during the progression of THe Recursive Algorithm of Life.
AS the name states this Algorithm is recursive, its base case is:
if(Human.lifeStatus == DEATH)
Where death is a defined int used as a flag to determine the living state or lifeStatus of the human.
Return Type:
A custom created type know as “fallType”.
fallType is basically an int:= 1 fallOfNobles
2 limboFall
3 fallOfSimpletons
Upon the death of a human depending on how far he progressed the fallType typeDef will return:=
1 If the Algorithm was a success
2 If the Algorithm progressed but did not reach the success case
3 If the Algorithm was a failure - Failure in the sense that the human did not improve.
Only Strivers can return 1 and only Simpletons can return 3.
Note however that the input is not designated right away as "Striver" "Simpleton". The input is Human and depending on the progression it either points in the direction of the Striver child class (leads to return type of fallType 1 or 2). Or it points in the direction of Simpletons (leads to returns of typeDef 2).
Progression and How it Runs:
The input humans start at state Human.lifeStatus() = BIRTH;
The AI of the humans then progresses and we get three cases:
CaSe 1: The Simpletons and their Fall
Simpletons take what they are given and are content with it. They use it for their living functions that return no incrimination on their initial byte size and at the end of their days when (Simpleton) Human.lifeStatus == DEATH they plummet from to their grave.
CaSe 2: The Strivers
Sub Case 2.1: limboFall
Strivers are also born with the same byteSize as the Simpletons which is the basic byteSize of a human. They also use it for their living functions but the AI of strivers triggers a chunk of functions know as the Human.improve() or Human.strive() (which is where they get their name from). The strivers seek something better, they don't know what it is exactly they can only feel it. They eventually realize that in order to progress their initial ByteSize is NOT enough. At this point hey call Human.strive() which basically allocates an area of bytes that they borrow and use for expanding. When (Striver)Human.strive() is called again that area is reallocated. Unfortunately since Strivers have to waste processing time on .strive() functions they often affect the duration of time needed to reach their Success Case, the Personal Legend*. In the case of the strivers that return the limboFall the duration required for them to hit their personal legend surpasses and is far greater then the lifeTime designated to that human. So they die before reaching their personal Legend.
Sub Case 2.2: The Nobles
Author: Daniel "Loony" Haddad
Version: 1.0
Input:
THe Recursive Algorithm of Life takes as input Humans.
The “Humans” class has two main children: 1. Strivers
2. Simpletons
Both Strivers and Simpletons are created with the same allocation of bytes.
The only notable difference between the Strivers and the Simpletons or basically what sets them apart is only discovered upon running or during the progression of THe Recursive Algorithm of Life.
AS the name states this Algorithm is recursive, its base case is:
if(Human.lifeStatus == DEATH)
Where death is a defined int used as a flag to determine the living state or lifeStatus of the human.
Return Type:
A custom created type know as “fallType”.
fallType is basically an int:= 1 fallOfNobles
2 limboFall
3 fallOfSimpletons
Upon the death of a human depending on how far he progressed the fallType typeDef will return:=
1 If the Algorithm was a success
2 If the Algorithm progressed but did not reach the success case
3 If the Algorithm was a failure - Failure in the sense that the human did not improve.
Only Strivers can return 1 and only Simpletons can return 3.
Note however that the input is not designated right away as "Striver" "Simpleton". The input is Human and depending on the progression it either points in the direction of the Striver child class (leads to return type of fallType 1 or 2). Or it points in the direction of Simpletons (leads to returns of typeDef 2).
Progression and How it Runs:
The input humans start at state Human.lifeStatus() = BIRTH;
The AI of the humans then progresses and we get three cases:
CaSe 1: The Simpletons and their Fall
Simpletons take what they are given and are content with it. They use it for their living functions that return no incrimination on their initial byte size and at the end of their days when (Simpleton) Human.lifeStatus == DEATH they plummet from to their grave.
CaSe 2: The Strivers
Sub Case 2.1: limboFall
Strivers are also born with the same byteSize as the Simpletons which is the basic byteSize of a human. They also use it for their living functions but the AI of strivers triggers a chunk of functions know as the Human.improve() or Human.strive() (which is where they get their name from). The strivers seek something better, they don't know what it is exactly they can only feel it. They eventually realize that in order to progress their initial ByteSize is NOT enough. At this point hey call Human.strive() which basically allocates an area of bytes that they borrow and use for expanding. When (Striver)Human.strive() is called again that area is reallocated. Unfortunately since Strivers have to waste processing time on .strive() functions they often affect the duration of time needed to reach their Success Case, the Personal Legend*. In the case of the strivers that return the limboFall the duration required for them to hit their personal legend surpasses and is far greater then the lifeTime designated to that human. So they die before reaching their personal Legend.
Sub Case 2.2: The Nobles
Similar to Sub Case 2.1 theFallOfNobles is returned when the time needed for a Striver to hit his personal legend is less then the lifeTime designated to that Human. That is why "The Fall of Nobles" is curved, in the remaining time those strivers enjoy a state of nobility in which they use nobleLivingFunctions() that are now accessible to them since they have an abundance of bytes to perform them.
Fig.1 Is the graphical representation of this Algorithm.
**************************************************************************************/
NOTE: "Personal Legend" is not my term, it's taken from a book called The Alchemist for Paulo Coelho
