Late nighters?

[GodBeastX]

I'll probably be logging in around 2 AM EST to pick on people. Anyone who wants to be picked on, be there, that's all I'm saying!

Also, if your company says "Dude, let's do extreme programming, it'll be great Bro!" Find a new job.

[Maevan2]

Also, if your company says "Dude, let's do extreme programming, it'll be great Bro!" Find a new job.

Can't find anybody who wants to work with you on your code?

[GodBeastX]

Extreme programming is this system that changes your company and makes the programmer the bottleneck.

Essentially it means coder burn out.

[DM_Equinox]

Actually, when my old employer started extreme programming, things started getting way better. Too late to save the company though. But I'm a believer!

[Twisted-Indoctrine]

... What the heck is extreme programming?

"Well in an effort to combat the drearyness that affornts morale in the office space we're now moving our operation to the back of this cargo plane. You will be encouraged to take inspiration for your coding while skydiving!" ?

[roguethree]

Extreme Programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development,[1][2][3] it advocates frequent "releases" in short development cycles (timeboxing), which is intended to improve productivity and introduce checkpoints where new customer requirements can be adopted.
Other elements of extreme programming include: programming in pairs or doing extensive code review, unit testing of all code, avoiding programming of features until they are actually needed, a flat management structure, simplicity and clarity in code, expecting changes in the customer's requirements as time passes and the problem is better understood, and frequent communication with the customer and among programmers.[2][3][4] The methodology takes its name from the idea that the beneficial elements of traditional software engineering practices are taken to "extreme" levels, on the theory that if some is good, more is better. It is unrelated to "cowboy coding", which is more free-form and unplanned. It does not advocate "death march" work schedules, but instead working at a sustainable pace.[5]
Critics have noted several potential drawbacks,[6] including problems with unstable requirements, no documented compromises of user conflicts, and lack of an overall design specification or document.

You poor guy. I don't code, but that looks like ass.

[Infallius_Daemonium]

This:

[GodBeastX]

Yall got jokes