Coder: Difference between revisions

51 bytes added ,  18:04, 13 November 2013
no edit summary
imported>Miauw
(Created Coder.)
 
imported>Miauw
No edit summary
Line 14: Line 14:


=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 tough, 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.


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.
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.]]


=The Source Code=
=The Source Code=
Anonymous user