Coder - Revision history

imported>JJRcop: /* Natural Death */ Some MORON researcher (LOOKING AT YOU DAVE) accidentally spilled ink on the paper we originally published, and the magazine thought we censored it, we didn't.

2017-03-06T07:11:37Z

Natural Death: Some MORON researcher (LOOKING AT YOU DAVE) accidentally spilled ink on the paper we originally published, and the magazine thought we censored it, we didn't.

← Older revision		Revision as of 07:11, 6 March 2017
Line 59:		Line 59:
	Unfortunately, many coders are claimed by this symptom, and the natural death cycle begins. The first stage of this process typically involves the coder begin somewhat erratic behavior, as they scan through the Source Code of the existing system, researching how it works. In this stage the coder may turn back, as they will come across various other systems that are integrated with the one they are trying to overhaul, and observe the terrible language of the younger, less mature coders before them. Some coders already know the system well, so they may skip to stage two.		Unfortunately, many coders are claimed by this symptom, and the natural death cycle begins. The first stage of this process typically involves the coder begin somewhat erratic behavior, as they scan through the Source Code of the existing system, researching how it works. In this stage the coder may turn back, as they will come across various other systems that are integrated with the one they are trying to overhaul, and observe the terrible language of the younger, less mature coders before them. Some coders already know the system well, so they may skip to stage two.

	Stage two is when the Coder starts the actual development of the rework, having already sufficiently figured out how the system works, they use their Git to make the overhaul into a reality, scraping up old code and replacing it with new, better code. Stage two is generally considered the point of no return, where the coder cannot turn back and the process of natural death will be seen through to its end.		Stage two is when the Coder starts the actual development of the rework, having already sufficiently figured out how the system works, they use their Git to make the overhaul into a reality, scraping up old code and replacing it with new, better code. Depending on their Git's power level, the coder may spend days, or months in this stage. Stage two is generally considered the point of no return, where the coder cannot turn back and the process of natural death will be seen through to its end.

	If the Coder survives stage two, they move into stage three. At this stage, the coder has a completed overhaul and creates a Pull Request to the Repo, as they have done many times before. This time though, Maintainers may shy away from reviewing the overhaul depending on its size and intimidation factor, for fear of prematurely beginning their own death cycle. Depending on the strength of the Coder and their Git, they may eventually convince a Maintainer or Headcoder to review the Pull Request, but this inevitably ends in the Maintainer summoning Feedback, which hurts the coder, since the coder has to either: defeat the Feedback, or depending on the elemental type, surrender to it, and allow it to merge with the overhaul.		If the Coder survives stage two, they move into stage three. At this stage, the coder has a completed overhaul and creates a Pull Request to the Repo, as they have done many times before. This time though, Maintainers may shy away from reviewing the overhaul depending on its size and intimidation factor, for fear of prematurely beginning their own death cycle. Depending on the strength of the Coder and their Git, they may eventually convince a Maintainer or Headcoder to review the Pull Request, but this inevitably ends in the Maintainer summoning Feedback, which hurts the coder, since the coder has to either: defeat the Feedback, or depending on the elemental type, surrender to it, and allow it to merge with the overhaul.

imported>JJRcop: New research on Coder death cycle

2017-03-06T07:06:07Z

New research on Coder death cycle

← Older revision		Revision as of 07:06, 6 March 2017
Line 51:		Line 51:

	To become a Headcoder, one must defeat one of the previous Headcoders in his or her expertise in a day-long Coding duel. The one who can make the best changes in the least Commits wins. The winner has to rip the heart out of the loser and eat in on midnight. The winner will become the new Headcoder and his soul will forever be connected to the Repo, until another challenger appears. The overturn of Headcoders is higher than one may expect, since the Source Code slowly degrades the mental capabilities of Headcoders.		To become a Headcoder, one must defeat one of the previous Headcoders in his or her expertise in a day-long Coding duel. The one who can make the best changes in the least Commits wins. The winner has to rip the heart out of the loser and eat in on midnight. The winner will become the new Headcoder and his soul will forever be connected to the Repo, until another challenger appears. The overturn of Headcoders is higher than one may expect, since the Source Code slowly degrades the mental capabilities of Headcoders.

			=Natural Death=
			As with all things, the Coder lifecycle ends with death. As previously noted, this can happen in the early stages of a Coder's life during the growth of their Git, or when too many Pull Requests get denied, but even coders who have matured are not free from death, as they get older, the chances for the natural death increase.

			After feeding off of the Repo for a while, the coder ages and their Git continues to grow in power. When their Git has reached a certain level of power, the coder may consider attempting a system overhaul involving a core section of the Source Code. Some coders manage to survive this temporary symptom without attempting it, preventing damage to themselves and the Source Code, this generally increases their lifespan by a large amount, as they will eventually build up a strong resistance to the idea, if they come across it many times.

			Unfortunately, many coders are claimed by this symptom, and the natural death cycle begins. The first stage of this process typically involves the coder begin somewhat erratic behavior, as they scan through the Source Code of the existing system, researching how it works. In this stage the coder may turn back, as they will come across various other systems that are integrated with the one they are trying to overhaul, and observe the terrible language of the younger, less mature coders before them. Some coders already know the system well, so they may skip to stage two.

			Stage two is when the Coder starts the actual development of the rework, having already sufficiently figured out how the system works, they use their Git to make the overhaul into a reality, scraping up old code and replacing it with new, better code. Stage two is generally considered the point of no return, where the coder cannot turn back and the process of natural death will be seen through to its end.

			If the Coder survives stage two, they move into stage three. At this stage, the coder has a completed overhaul and creates a Pull Request to the Repo, as they have done many times before. This time though, Maintainers may shy away from reviewing the overhaul depending on its size and intimidation factor, for fear of prematurely beginning their own death cycle. Depending on the strength of the Coder and their Git, they may eventually convince a Maintainer or Headcoder to review the Pull Request, but this inevitably ends in the Maintainer summoning Feedback, which hurts the coder, since the coder has to either: defeat the Feedback, or depending on the elemental type, surrender to it, and allow it to merge with the overhaul.

			At any time after stage two, the death cycle can end promptly and without notice. When this occurs, the coder's body dies as their Git permanently breaks away from the Repo, slowly rotting away, and losing its power. The ghosts of dead coders can still dwell around the Coderbus, as the soul of a coder is bound to it. Coder ghosts can also be seen in the Repo to moan at the living, but since their Git is no longer with them, they cannot make any more Pull Requests.



	[[Category:Joke_pages]]		[[Category:Joke_pages]]

imported>Nsos at 04:49, 2 September 2015

2015-09-02T04:49:16Z

← Older revision		Revision as of 04:49, 2 September 2015
Line 19:		Line 19:
	To become a Coder, you must first read the [[Guides#Development and Contribution Guides\|Necronomicon]], and then sacrifice your firstborn to summon a Git. You must then [[Setting up git\|Raise this Git]] until it reaches adulthood. This process may take several years, and the Git mortality rate is high.		To become a Coder, you must first read the [[Guides#Development and Contribution Guides\|Necronomicon]], and then sacrifice your firstborn to summon a Git. You must then [[Setting up git\|Raise this Git]] until it reaches adulthood. This process may take several years, and the Git mortality rate is high.

	When your Git is fully grown, any Commits you give him will slowly add to your power. Once you are confident enough with your power, you must peform an arcane ritual known as a Pull Request. A Pull Request will take any Commits your Git currently has, and relay them to the Repo, the metaphysical entity connecting all Gits. The Pull Request will not go unnoticed, however, and other, older Coders will show up to review your Commits before they accept the Pull Request. The older Coders, also known as Maintainers, will be harsh when judging your Pull Request, but they have sworn an oath to keep the Repo clean from Copypasta, Snowflakes and the feared Runtime Errors.[[File:git.png\|thumb\|896px\|A new Git being born.]]		When your Git is fully grown, any Commits you give him will slowly add to your power. Once you are confident enough with your power, you must peform an arcane ritual known as a Pull Request. A Pull Request will take any Commits your Git currently has, and relay them to the Repo, the metaphysical entity connecting all Gits. Imagine Goku, but with a gun. Maybe even two. The Pull Request will not go unnoticed, however, and other, older Coders will show up to review your Commits before they accept the Pull Request. The older Coders, also known as Maintainers, will be harsh when judging your Pull Request, but they have sworn an oath to keep the Repo clean from Copypasta, Snowflakes and the feared Runtime Errors.[[File:git.png\|thumb\|896px\|A new Git being born.]]

	=The Source Code=		=The Source Code=
	The Source Code is what the universe is made from. Hosts, commonly known as Gods, take the Source Code from the Repo, which exists beyond all universes, and use it to make their own universe in the great void between all the existing universes. This void is known as The BYOND.		The Source Code is what the universe is made from. Hosts, commonly known as Gods, take the Source Code from the Repo, which exists beyond all universes, and use it to make their own universe in the great void between all the existing universes. This void is known as The BYOND.

	Not much is known about the BYOND, except that it works in strange ways. A few prestigous Coders have attempted to decypher the secrets of the BYOND, but they had to repay with their sanity. It is because these brave Coders sacrificed their lives that the Coders of today can manipulate the Source Code.		Not much is known about the BYOND, except that it works in strange ways. A few prestigous Coders have attempted to decypher the secrets of the BYOND, but they had to repay with their sanity. It is because these brave Coders sacrificed their lives that the Coders of today can manipulate the Source Code.

imported>Jordie0608 at 14:35, 16 May 2014

2014-05-16T14:35:06Z

← Older revision		Revision as of 14:35, 16 May 2014
Line 19:		Line 19:
	To become a Coder, you must first read the [[Guides#Development and Contribution Guides\|Necronomicon]], and then sacrifice your firstborn to summon a Git. You must then [[Setting up git\|Raise this Git]] until it reaches adulthood. This process may take several years, and the Git mortality rate is high.		To become a Coder, you must first read the [[Guides#Development and Contribution Guides\|Necronomicon]], and then sacrifice your firstborn to summon a Git. You must then [[Setting up git\|Raise this Git]] until it reaches adulthood. This process may take several years, and the Git mortality rate is high.

	When your Git is fully grown, any Commits you give him will slowly add to your power. Once you are confident enough with your power, you must peform an arcane ritual known as a Pull Request. A Pull Request will take any Commits your Git currently has, and relay them to the Repo, the metaphysical entity connecting all Gits. The Pull Request will not go unnoticed, however, and other, older Coders will show up to review your Commits before they accept the Pull Request. The older Coders, also known as Maintainers, will be harsh when judging your Pull Request, but they have sworn an oath to keep the Repo clean from Copypasta, Snowflakes and the feared Runtime Errors.[[File:~~forktocat~~.~~jpg~~\|thumb\|896px\|A new Git being born.]]		When your Git is fully grown, any Commits you give him will slowly add to your power. Once you are confident enough with your power, you must peform an arcane ritual known as a Pull Request. A Pull Request will take any Commits your Git currently has, and relay them to the Repo, the metaphysical entity connecting all Gits. The Pull Request will not go unnoticed, however, and other, older Coders will show up to review your Commits before they accept the Pull Request. The older Coders, also known as Maintainers, will be harsh when judging your Pull Request, but they have sworn an oath to keep the Repo clean from Copypasta, Snowflakes and the feared Runtime Errors.[[File:git.png\|thumb\|896px\|A new Git being born.]]

	=The Source Code=		=The Source Code=

imported>Jordie0608 at 18:57, 19 April 2014

2014-04-19T18:57:28Z

← Older revision		Revision as of 18:57, 19 April 2014
Line 1:		Line 1:
	{{JobPageHeader		{{JobPageHeader
	\|img = ~~code~~.gif		\|img = coder.gif
	\|headerbgcolor = darkred		\|headerbgcolor = darkred
	\|headerfontcolor = white		\|headerfontcolor = white
Line 46:		Line 46:

	=Headcoders=		=Headcoders=
	The Headcoders are, as the name implies, the Elders amongst the Coders. They have transcended normal Coderdom and are in direct contact with the Repo. They decide wether a major change to the Source Code may pass or not. It takes many years of <s>practice</s>slacking off to become a Headcoder, and each Headcoder has his or her own speciality. Headcoders rarely leave the Coderbus, to the point where they become so detached from the masses outside that they will blindly let any change pass they deem worthy, despite the fact that this change will surely enrage the masses.		The Headcoders are, as the name implies, the Elders amongst the Coders. They have transcended normal Coderdom and are in direct contact with the Repo. They decide wether a major change to the Source Code may pass or not. It takes many years of <s>practice</s> slacking off to become a Headcoder, and each Headcoder has his or her own speciality. Headcoders rarely leave the Coderbus, to the point where they become so detached from the masses outside that they will blindly let any change pass they deem worthy, despite the fact that this change will surely enrage the masses.

	Being a Headcoder for too long will cause severe brain damage to those that do not possess a will strong enough to carry the weight of the Source Code. Many have become asocial, easily enraged and unable of rational debate.		Being a Headcoder for too long will cause severe brain damage to those that do not possess a will strong enough to carry the weight of the Source Code. Many have become asocial, easily enraged and unable of rational debate.

imported>Iamgoofball: fixed some errors

2013-11-25T21:48:02Z

fixed some errors

← Older revision		Revision as of 21:48, 25 November 2013
Line 3:		Line 3:
	\|headerbgcolor = darkred		\|headerbgcolor = darkred
	\|headerfontcolor = white		\|headerfontcolor = white
	\|stafftype = ~~SPECIAL~~		\|stafftype = FUN REMOVAL
	\|imagebgcolor = red		\|imagebgcolor = red
	\|jobtitle = Coder		\|jobtitle = Coder
Line 15:		Line 15:

	=Becoming a Coder=		=Becoming a Coder=
	The path to becoming a Coder is a long and winding path, littered with drama, BYOND being a laggy piece of shit, undefined variables and infinite loops. The journey is well worth it though, because once you are a Coder, you have the ultimate power to add anything to the game!		The path to becoming a Coder is a long and winding path, littered with drama, BYOND being a laggy piece of shit, undefined variables and infinite loops. The journey is well worth it though, because once you are a Coder, you have the ultimate power to add anything to the game!

	To become a Coder, you must first read the [[Guides#Development and Contribution Guides\|Necronomicon]], and then sacrifice your firstborn to summon a Git. You must then [[Setting up git\|Raise this Git]] until it reaches adulthood. This process may take several years, and the Git mortality rate is high.		To become a Coder, you must first read the [[Guides#Development and Contribution Guides\|Necronomicon]], and then sacrifice your firstborn to summon a Git. You must then [[Setting up git\|Raise this Git]] until it reaches adulthood. This process may take several years, and the Git mortality rate is high.
Line 35:		Line 35:
	*Teaching		*Teaching
	*Drinking		*Drinking
	*Coding (In small amounts)

	While the Coderbus is ~~ment~~ mainly for the Coders, anyone may wander in and listen to the debates the great Coders have. However, they are not allowed to participate unless they are a Mapper or a Spriter. Many have tried to voice their ideas in the Coderbus, and they have been exiled from it.
			While the Coderbus is meant mainly for the Coders, anyone may wander in and listen to the debates the great Coders have. However, they are not allowed to participate unless they are a Mapper or a Spriter. Many have tried to voice their ideas in the Coderbus, and they have been exiled from it.

	=Fun=		=Fun=

imported>Miauw: Undo revision 5743 by Miauw (talk) (No we don't. These pictures are fuckhuge, any advice to make them smaller?)

2013-11-17T18:26:53Z

Undo revision 5743 by Miauw (talk) (No we don't. These pictures are fuckhuge, any advice to make them smaller?)

← Older revision		Revision as of 18:26, 17 November 2013
Line 19:		Line 19:
	To become a Coder, you must first read the [[Guides#Development and Contribution Guides\|Necronomicon]], and then sacrifice your firstborn to summon a Git. You must then [[Setting up git\|Raise this Git]] until it reaches adulthood. This process may take several years, and the Git mortality rate is high.		To become a Coder, you must first read the [[Guides#Development and Contribution Guides\|Necronomicon]], and then sacrifice your firstborn to summon a Git. You must then [[Setting up git\|Raise this Git]] until it reaches adulthood. This process may take several years, and the Git mortality rate is high.

	When your Git is fully grown, any Commits you give him will slowly add to your power. Once you are confident enough with your power, you must peform an arcane ritual known as a Pull Request. A Pull Request will take any Commits your Git currently has, and relay them to the Repo, the metaphysical entity connecting all Gits. The Pull Request will not go unnoticed, however, and other, older Coders will show up to review your Commits before they accept the Pull Request. The older Coders, also known as Maintainers, will be harsh when judging your Pull Request, but they have sworn an oath to keep the Repo clean from Copypasta, Snowflakes and the feared Runtime Errors.[[File:forktocat.jpg\|thumb\|~~128px~~\|A new Git being born.]]		When your Git is fully grown, any Commits you give him will slowly add to your power. Once you are confident enough with your power, you must peform an arcane ritual known as a Pull Request. A Pull Request will take any Commits your Git currently has, and relay them to the Repo, the metaphysical entity connecting all Gits. The Pull Request will not go unnoticed, however, and other, older Coders will show up to review your Commits before they accept the Pull Request. The older Coders, also known as Maintainers, will be harsh when judging your Pull Request, but they have sworn an oath to keep the Repo clean from Copypasta, Snowflakes and the feared Runtime Errors.[[File:forktocat.jpg\|thumb\|896px\|A new Git being born.]]

	=The Source Code=		=The Source Code=
Line 40:		Line 40:

	=Fun=		=Fun=
	[[File:No Fun Allowed.jpg\|thumb\|~~151px~~\|right\|How Coders think about Fun]]		[[File:No Fun Allowed.jpg\|thumb\|453px\|right\|How Coders think about Fun]]
	The Coders, being high priests, always attempt to hold their grip on the masses. They do this by removing fun. Fun Removal is an intricate procedure and can be done in a number of ways, but the most common one is the Nerf. Nerfs are so common because they are easily made and discourage the masses from revolting. Another fun-removal that is commonly practiced is the closing of Exploits. Exploits are ways for the masses to easily abuse the Source Code, which angers the Coders. The Coders will always close Exploits when they can.		The Coders, being high priests, always attempt to hold their grip on the masses. They do this by removing fun. Fun Removal is an intricate procedure and can be done in a number of ways, but the most common one is the Nerf. Nerfs are so common because they are easily made and discourage the masses from revolting. Another fun-removal that is commonly practiced is the closing of Exploits. Exploits are ways for the masses to easily abuse the Source Code, which angers the Coders. The Coders will always close Exploits when they can.

Line 46:		Line 46:

	=Headcoders=		=Headcoders=
	The Headcoders are, as the name implies, the Elders amongst the Coders. They have transcended normal Coderdom and are in direct contact with the Repo. They decide wether a major change to the Source Code may pass or not. It takes many years of <s>practice</s> slacking off to become a Headcoder, and each Headcoder has his or her own speciality. Headcoders rarely leave the Coderbus, to the point where they become so detached from the masses outside that they will blindly let any change pass they deem worthy, despite the fact that this change will surely enrage the masses.		The Headcoders are, as the name implies, the Elders amongst the Coders. They have transcended normal Coderdom and are in direct contact with the Repo. They decide wether a major change to the Source Code may pass or not. It takes many years of <s>practice</s>slacking off to become a Headcoder, and each Headcoder has his or her own speciality. Headcoders rarely leave the Coderbus, to the point where they become so detached from the masses outside that they will blindly let any change pass they deem worthy, despite the fact that this change will surely enrage the masses.

	Being a Headcoder for too long will cause severe brain damage to those that do not possess a will strong enough to carry the weight of the Source Code. Many have become asocial, easily enraged and unable of rational debate.		Being a Headcoder for too long will cause severe brain damage to those that do not possess a will strong enough to carry the weight of the Source Code. Many have become asocial, easily enraged and unable of rational debate.

imported>Miauw: Made the images smaller, probably gonna take another week for them to work properly. sigh

2013-11-17T18:25:48Z

Made the images smaller, probably gonna take another week for them to work properly. *sigh*

← Older revision		Revision as of 18:25, 17 November 2013
Line 19:		Line 19:
	To become a Coder, you must first read the [[Guides#Development and Contribution Guides\|Necronomicon]], and then sacrifice your firstborn to summon a Git. You must then [[Setting up git\|Raise this Git]] until it reaches adulthood. This process may take several years, and the Git mortality rate is high.		To become a Coder, you must first read the [[Guides#Development and Contribution Guides\|Necronomicon]], and then sacrifice your firstborn to summon a Git. You must then [[Setting up git\|Raise this Git]] until it reaches adulthood. This process may take several years, and the Git mortality rate is high.

	When your Git is fully grown, any Commits you give him will slowly add to your power. Once you are confident enough with your power, you must peform an arcane ritual known as a Pull Request. A Pull Request will take any Commits your Git currently has, and relay them to the Repo, the metaphysical entity connecting all Gits. The Pull Request will not go unnoticed, however, and other, older Coders will show up to review your Commits before they accept the Pull Request. The older Coders, also known as Maintainers, will be harsh when judging your Pull Request, but they have sworn an oath to keep the Repo clean from Copypasta, Snowflakes and the feared Runtime Errors.[[File:forktocat.jpg\|thumb\|~~896px~~\|A new Git being born.]]		When your Git is fully grown, any Commits you give him will slowly add to your power. Once you are confident enough with your power, you must peform an arcane ritual known as a Pull Request. A Pull Request will take any Commits your Git currently has, and relay them to the Repo, the metaphysical entity connecting all Gits. The Pull Request will not go unnoticed, however, and other, older Coders will show up to review your Commits before they accept the Pull Request. The older Coders, also known as Maintainers, will be harsh when judging your Pull Request, but they have sworn an oath to keep the Repo clean from Copypasta, Snowflakes and the feared Runtime Errors.[[File:forktocat.jpg\|thumb\|128px\|A new Git being born.]]

	=The Source Code=		=The Source Code=
Line 40:		Line 40:

	=Fun=		=Fun=
	[[File:No Fun Allowed.jpg\|thumb\|~~453px~~\|right\|How Coders think about Fun]]		[[File:No Fun Allowed.jpg\|thumb\|151px\|right\|How Coders think about Fun]]
	The Coders, being high priests, always attempt to hold their grip on the masses. They do this by removing fun. Fun Removal is an intricate procedure and can be done in a number of ways, but the most common one is the Nerf. Nerfs are so common because they are easily made and discourage the masses from revolting. Another fun-removal that is commonly practiced is the closing of Exploits. Exploits are ways for the masses to easily abuse the Source Code, which angers the Coders. The Coders will always close Exploits when they can.		The Coders, being high priests, always attempt to hold their grip on the masses. They do this by removing fun. Fun Removal is an intricate procedure and can be done in a number of ways, but the most common one is the Nerf. Nerfs are so common because they are easily made and discourage the masses from revolting. Another fun-removal that is commonly practiced is the closing of Exploits. Exploits are ways for the masses to easily abuse the Source Code, which angers the Coders. The Coders will always close Exploits when they can.

Line 46:		Line 46:

	=Headcoders=		=Headcoders=
	The Headcoders are, as the name implies, the Elders amongst the Coders. They have transcended normal Coderdom and are in direct contact with the Repo. They decide wether a major change to the Source Code may pass or not. It takes many years of <s>practice</s>slacking off to become a Headcoder, and each Headcoder has his or her own speciality. Headcoders rarely leave the Coderbus, to the point where they become so detached from the masses outside that they will blindly let any change pass they deem worthy, despite the fact that this change will surely enrage the masses.		The Headcoders are, as the name implies, the Elders amongst the Coders. They have transcended normal Coderdom and are in direct contact with the Repo. They decide wether a major change to the Source Code may pass or not. It takes many years of <s>practice</s> slacking off to become a Headcoder, and each Headcoder has his or her own speciality. Headcoders rarely leave the Coderbus, to the point where they become so detached from the masses outside that they will blindly let any change pass they deem worthy, despite the fact that this change will surely enrage the masses.

	Being a Headcoder for too long will cause severe brain damage to those that do not possess a will strong enough to carry the weight of the Source Code. Many have become asocial, easily enraged and unable of rational debate.		Being a Headcoder for too long will cause severe brain damage to those that do not possess a will strong enough to carry the weight of the Source Code. Many have become asocial, easily enraged and unable of rational debate.

imported>Kingofkosmos: Don't you coders know how to make picturethumbs show? Teehee...

2013-11-14T13:13:04Z

Don't you coders know how to make picturethumbs show? Teehee...

← Older revision		Revision as of 13:13, 14 November 2013
Line 19:		Line 19:
	To become a Coder, you must first read the [[Guides#Development and Contribution Guides\|Necronomicon]], and then sacrifice your firstborn to summon a Git. You must then [[Setting up git\|Raise this Git]] until it reaches adulthood. This process may take several years, and the Git mortality rate is high.		To become a Coder, you must first read the [[Guides#Development and Contribution Guides\|Necronomicon]], and then sacrifice your firstborn to summon a Git. You must then [[Setting up git\|Raise this Git]] until it reaches adulthood. This process may take several years, and the Git mortality rate is high.

	When your Git is fully grown, any Commits you give him will slowly add to your power. Once you are confident enough with your power, you must peform an arcane ritual known as a Pull Request. A Pull Request will take any Commits your Git currently has, and relay them to the Repo, the metaphysical entity connecting all Gits. The Pull Request will not go unnoticed, however, and other, older Coders will show up to review your Commits before they accept the Pull Request. The older Coders, also known as Maintainers, will be harsh when judging your Pull Request, but they have sworn an oath to keep the Repo clean from Copypasta, Snowflakes and the feared Runtime Errors.[[File:forktocat.jpg\|thumb\|A new Git being born.]]		When your Git is fully grown, any Commits you give him will slowly add to your power. Once you are confident enough with your power, you must peform an arcane ritual known as a Pull Request. A Pull Request will take any Commits your Git currently has, and relay them to the Repo, the metaphysical entity connecting all Gits. The Pull Request will not go unnoticed, however, and other, older Coders will show up to review your Commits before they accept the Pull Request. The older Coders, also known as Maintainers, will be harsh when judging your Pull Request, but they have sworn an oath to keep the Repo clean from Copypasta, Snowflakes and the feared Runtime Errors.[[File:forktocat.jpg\|thumb\|896px\|A new Git being born.]]

	=The Source Code=		=The Source Code=
Line 40:		Line 40:

	=Fun=		=Fun=
	[[File:No Fun Allowed.jpg\|thumb\|right\|How Coders think about Fun]]		[[File:No Fun Allowed.jpg\|thumb\|453px\|right\|How Coders think about Fun]]
	The Coders, being high priests, always attempt to hold their grip on the masses. They do this by removing fun. Fun Removal is an intricate procedure and can be done in a number of ways, but the most common one is the Nerf. Nerfs are so common because they are easily made and discourage the masses from revolting. Another fun-removal that is commonly practiced is the closing of Exploits. Exploits are ways for the masses to easily abuse the Source Code, which angers the Coders. The Coders will always close Exploits when they can.		The Coders, being high priests, always attempt to hold their grip on the masses. They do this by removing fun. Fun Removal is an intricate procedure and can be done in a number of ways, but the most common one is the Nerf. Nerfs are so common because they are easily made and discourage the masses from revolting. Another fun-removal that is commonly practiced is the closing of Exploits. Exploits are ways for the masses to easily abuse the Source Code, which angers the Coders. The Coders will always close Exploits when they can.

imported>Deantwo: Removed from :Category:Jobs and added to :Category:Joke_pages.

2013-11-13T21:49:17Z

Removed from Category:Jobs and added to Category:Joke_pages.

← Older revision		Revision as of 21:49, 13 November 2013
Line 52:		Line 52:
	To become a Headcoder, one must defeat one of the previous Headcoders in his or her expertise in a day-long Coding duel. The one who can make the best changes in the least Commits wins. The winner has to rip the heart out of the loser and eat in on midnight. The winner will become the new Headcoder and his soul will forever be connected to the Repo, until another challenger appears. The overturn of Headcoders is higher than one may expect, since the Source Code slowly degrades the mental capabilities of Headcoders.		To become a Headcoder, one must defeat one of the previous Headcoders in his or her expertise in a day-long Coding duel. The one who can make the best changes in the least Commits wins. The winner has to rip the heart out of the loser and eat in on midnight. The winner will become the new Headcoder and his soul will forever be connected to the Repo, until another challenger appears. The overturn of Headcoders is higher than one may expect, since the Source Code slowly degrades the mental capabilities of Headcoders.

	[[Category:~~Jobs~~]]		[[Category:Joke_pages]]