Coder: Difference between revisions
Don't you coders know how to make picturethumbs show? Teehee...
imported>Deantwo (Removed from Category:Jobs and added to Category:Joke_pages.) |
imported>Kingofkosmos (Don't you coders know how to make picturethumbs show? Teehee...) |
||
| 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. | ||