Extreme programming

From Uncyclopedia, the content-free encyclopedia
Jump to navigation Jump to search


For those without comedic tastes, the so-called experts at Wikipedia have an article about X-treme Programming.
Extreme Programmer Larry "Gnarly" Johnson slays an epic rail while refactoring a haggard Java class.
The late John "Danger" Platt (Team Microsoft) debugs a tricky .NET framework shortly before his bloody demise.

X-treme Programming (XP or eXtra-Puke) is a revolutionary software development methodology in which programmers write code whilst skiing down mountains, parachuting out of airplanes, being chased by ravenous sharks with fucking lasers, or participating in any of a wide variety of other extreme sports. The quick reflexes and split-second debugging skills needed to survive in these scenarios make agility and bravery a necessity among extreme programmers. This leads the sport to be far less popular than the traditional method of programming.

Studies have shown that software projects developed using the Extreme Programming methodology have a 64% faster time to market than projects developed using conventional methods. In addition, XP is over 65,536% more profitable as a spectator sport than conventional programming.

History[edit | edit source]

Extreme Programming was developed by Kent Beck after yet another enormously successful (but enormously boring) waterfall software project. They first practiced XP on the Krispy Kreme Korporation (K3) payroll project, which resulted in an unqualified success (in that Kent and Ward had a great time, were totally unqualified for the job, and they escaped before the fireball consumed the remains of the Korporate Headkwarters).

Hard Core Practices[edit | edit source]

Project Velocity[edit | edit source]

Extreme Programming emphasises the importance of moving people around, often at speeds exceeding 200 miles per hour. This speed is known as the "Project Velocity".

Frequent Small Releases[edit | edit source]

Also emphasised are frequent small releases of blood, feces, vomit, phlegm, etc. Not only is this therapeutic for the programmer, who is often required to program nonstop for up to 14 hours a day, this also looks absolutely spectacular on television.

Merciless Refracturing[edit | edit source]

On the rare occasions when an Extreme Programmer quails and runs back to base like a frightened schoolgirl, the rest of the team is encouraged to refracture any bones the programmer had previously broken.

Testosterone Driven Development[edit | edit source]

The watchword of Extreme Programming is "Testosterone First!" Not a line of code is written without macho posturing for the benefit of the cameras, the rest of the team and any Code Babes that are hanging around.

Unsustainable Pace[edit | edit source]

The key to Extreme Programming is setting an absurdly unsustainable pace (usually 200 miles per hour or more, which is necessary to maintain Project Velocity) and then forcing the programmer to sustain it or suffer an agonizing death.

Whole Team[edit | edit source]

Due to the high likelihood of injury or death, it is important to have a Whole Team of extreme programmers on hand at all times. When your first programmer gets his ankles crossed on the slopes and tumbles screaming off a cliff, you'll be glad you brought along a few backups.

Conclusion[edit | edit source]

It has been found that the intense fear and adrenaline rush produced by dangerous situations heightens the programmer's awareness and thus the quality of code produced, albeit at the cost of reducing the programmer's life expectancy (due to continuous disintegration). However, with colleges and universities churning out highly qualified young programmers at an astonishing rate, this is considered an acceptable and very cost-effective tradeoff.

Notable Extreme Programmers[edit | edit source]

See also[edit | edit source]

References[edit | edit source]