Extreme Programming

It's been a long time since the last discussion on this topic.

FOR A REASON, DUMBASS

It's shit.

XP only works if:

a) Everyone involved is honest with the team and themselves
b) The customer isn't a dumbass

>=1
It's been a long time since the last discussion on this topic.
Yeah, I, like, invented that meme.

FOR A REASON, DUMBASS
is now a meme.

>>4 >=1

>>6
haskell. haskell nomads.

>>7
Normal quoting is more monadic than that.

Not to mention it's also total bullshit, even if the customer isn't a dumbass, what customer has the time to stick around with a team of software engineers and answer all of their stupid questions? You're a fucking engineer, you're supposed to infer things and think with your head. Not bother the customer endlessly with questions.

It also has a lot of ENTERPRISE theory bullshit, like power struggles inside organizations and etc. Who cares, why is that even being discussed?

Also, the "LET'S JUST HACK SHIT UP AND REFACTOR CODE LATER" approach makes me want to kill puppies. What the fuck.

Fuck, XP is so shitty. Sometimes I wonder if all the new trends in computer engineering invented in the past 5-10 years exist solely for the purpose of pissing people off.

>>5
Go back to /b/, fucktard. Stop forcing your shitty "memes", no one gives a shit. They're supposed to propagate

>>9
There are plenty of business problems you know are solvable but nobody knows about the exact requirements needed to create a good set of specs. The best way to deal with those situations is to start work with what is known, maybe with a prototype, and keep refactoring the specs as there is a greater understanding of the requirements. When the specs change, it will also mean a change in the code which requires a team of programmers to be able to quickly reflect the changes in the specs. Eventually, you should have a good enough understanding of the problems involved to be able to complete the project fairly easily (as the team has already completed part of the project) or refactor the whole project one last time to implement changes that affect the foundation of the program(s).

>>9
congratulations, you are the reason the average person hates computers

>>11
Ｉ ｆｅｅｌ ｋｉｎｄ ｏｆ ｂａｄ ａｂｏｕｔ ｉｔ ：（

People actually write editors   They must not   meet many MySQL.

Lain.

All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy