User not logged in - login - register
Home Calendar Books School Tool Photo Gallery Message Boards Users Statistics Advertise Site Info
go to bottom | |
 Message Boards » » CSC - Extreme Programming Page [1]  
BigMan157
no u
103354 Posts
user info
edit post

wtf is it?

5/29/2007 5:56:48 PM

virga
All American
2019 Posts
user info
edit post

i believe the first result when you GOOGLE IT is relevant to your question.

5/29/2007 6:59:49 PM

ambrosia1231
eeeeeeeeeevil
76471 Posts
user info
edit post

via NCSUs computer training unit?

5/29/2007 7:29:18 PM

Aficionado
Suspended
22518 Posts
user info
edit post

rather than sit at a desk

you are programming on the side of a mountain, or in a cave, maybe scuba diving, talking to a girl, etc

you know, things that CSC majors find extreme

5/29/2007 10:49:47 PM

LadyWolff
All American
2286 Posts
user info
edit post

Oh for fuck's sake -

Extreme Programming or XP (not the OS) is a software engineering method. It's all about process and how you manage projects.

I believe the ACM library has the original paper on the subject, which you can access through NCSU"s library page (man, i'm gonna miss that database as an alum, i think i'm going to pay for an ACM membership or see if my employer has access to that database).

It's newer than say waterfall, spiral, etc.

And if that's not enough to get you started then you're too dumb to be thinking about CSC.

5/30/2007 1:35:19 AM

Specter
All American
6575 Posts
user info
edit post

5/30/2007 2:26:52 AM

mathman
All American
1631 Posts
user info
edit post

Quote :
"you are programming on the side of a mountain, or in a cave, maybe scuba diving, talking to a girl, etc"


nicely done.

5/30/2007 3:31:52 AM

Fry
The Stubby
7784 Posts
user info
edit post

ignore all but LadyWolff

bigman u been thinkin about csc?

[Edited on June 1, 2007 at 4:32 AM. Reason : ]

6/1/2007 4:30:49 AM

BigMan157
no u
103354 Posts
user info
edit post

no, i just came across the name the other day and wondered what it was

6/1/2007 8:31:03 AM

WolfAce
All American
6458 Posts
user info
edit post

i lol'd

6/4/2007 7:55:55 PM

Lionheart
I'm Eggscellent
12775 Posts
user info
edit post

puts us further away from the methodology needed to be a legitimate engineering discipline than we already are

6/4/2007 9:58:25 PM

Lionheart
I'm Eggscellent
12775 Posts
user info
edit post

Quote :
"The principles that form the basis of XP are based on the values just described and are intended to foster decisions in a system development project. The principles are intended to be more concrete than the values and more easily translated to guidance in a practical situation.

Feedback is most useful if it is done rapidly. The time between an action and its feedback is critical to learning and making changes. In Extreme Programming, unlike traditional system development methods, contact with the customer occurs in small iterations. The customer has clear insight into the system that is being developed. He or she can give feedback and steer the development as needed.

Unit tests also contribute to the rapid feedback principle. When writing code, the unit test provides direct feedback as to how the system reacts to the changes one has made. If, for instance, the changes affect a part of the system that is not in the scope of the programmer who made them, that programmer will not notice the flaw. There is a large chance that this bug will appear when the system is in production.

Assuming simplicity is about treating every problem as if its solution were "extremely simple". Traditional system development methods say to plan for the future and to code for reusability. Extreme programming rejects these ideas.

The advocates of Extreme Programming say that making big changes all at once does not work. Extreme Programming applies incremental changes: for example, a system might have small releases every three weeks. By making many little steps the customer has more control over the development process and the system that is being developed.

The principle of embracing change is about not working against changes but embracing them. For instance, if at one of the iterative meetings it appears that the customer's requirements have changed dramatically, programmers are to embrace this and plan the new requirements for the next iteration.
"


http://en.wikipedia.org/wiki/Extreme_programming#Principles

I can't say I'm not biased, I'm definately a traditionalist. The problem in my mind is that leaving things in such a state of flux and letting someone come in and change the specs at just about any time is a bad idea.

How bad would a building be if they made lots of changes to the plan throughout the building process etc

6/4/2007 10:01:37 PM

Lowjack
All American
10491 Posts
user info
edit post

It would be completely awesome.

6/4/2007 10:39:53 PM

pigkilla
All American
2332 Posts
user info
edit post

Quote :
"And if that's not enough to get you started then you're too dumb to be thinking about CSC."


i bet that this is a ugly bitch saying this hahahah

CAUSE ONLY HOT GIRLS DO CSC

6/5/2007 12:28:02 PM

esgargs
Suspended
97470 Posts
user info
edit post

Ignore - "And if that's not enough to get you started then you're too dumb to be thinking about CSC". Typical condescending BS statement from someone who doesn't know what they're talking about.

As for Extreme Programming, it's just one of the Agile Development Methodologies devised in the early 2000s. The focus is on spending less time on planning design artifacts, and more on actually producing or evolving the final product. One of the highlights is having an actual business person/customer interact with the development team very regularly (at least once a day), which could more often than not lead to problems in terms of finite requirements and deadlines/deliver ability.

I am not a big proponent of XP, as it seems to work only in research/educational settings. Real world corporate environments don't have enough time as well as monetary budgets. NCSU is big on the pair programming aspect of XP.

Apart from Wikipedia, be sure to read up some good resources on Agile Manifesto.

6/7/2007 4:47:14 PM

synchrony7
All American
4462 Posts
user info
edit post

Quote :
"I am not a big proponent of XP, as it seems to work only in research/educational settings."


Exactly. It's all nice and fuzzy in a theoretical sense (kind of like communism or Dr. Phil) but in reality is just annoying and has no practical application in real life.

[/thread]

6/13/2007 1:00:43 PM

rudeboy
All American
3049 Posts
user info
edit post

^I doubt it. We program XP in my company. It's good because our clients really don't know what they're looking for, so handing them new releases every couple of weeks helps out. We even hook up two monitors/mouse/keyboards at the same time. We are able to knock out small bugs much faster when two people who know the code well.

But at the same time, there are only 4 programmers in my company. When we get more on board, this will become harder. It also made it difficult when one of the developers was based in San Antonio. Communication is key.

6/13/2007 7:26:20 PM

Fry
The Stubby
7784 Posts
user info
edit post

i hated paired programming

btw,
Quote :
"How bad would a building be if they made lots of changes to the plan throughout the building process etc"

does happen... found that out working on construction sites for a while.

as for this,
Quote :
"you know, things that CSC majors find extreme"

CSC's are nerds!!! bwahahaha... geez. we're not all stuck in a permanent WoW state.

i agree with gargs and synchrony, especially when a dev team is say 10+... i don't want to see the chaos XP could have.. it's definitely prettier on paper. for simple, small project, sure, XP would be just fine, but i honestly believe that's about it

6/14/2007 4:47:08 AM

steviewonder
All American
6194 Posts
user info
edit post

Quote :
"And if that's not enough to get you started then you're too dumb to be thinking about CSC"


Anybody can do CSC, you just have to get past the douchebags that are already in it, and think that they are the upper crust of the universe. I came in as a soph, confused as hell about java and just trying to scrape by in 116, but in 216, I got the hang of it, and really loved the challenges that are inherent in CSC.

6/14/2007 10:53:03 AM

LadyWolff
All American
2286 Posts
user info
edit post

Let me explain what I meant by that- 1. i was in a bad mood when i posted that but 2. it should be enough information to point you in the direction to *find* more information and learn what it is.

I did *not* post a summary that would be sufficient for learning it, no.
And you can be quite intelligent enough for CSC and know nothing about the field, I was more making a comment that given a direction you need to be able to learn or else you aren't. (and frankly you arent then for most fields).

It's not about what you know, it's entirely about ability to learn, and to find things given a direction/starting point.



[Edited on June 14, 2007 at 4:07 PM. Reason : .]

6/14/2007 4:06:02 PM

Novicane
All American
15416 Posts
user info
edit post

Quote :
"It's not about what you know, it's entirely about ability to learn, and to find things given a direction/starting point."


truth.

As I will grad next year my csc degree i have seen it crush people who think they know it all and destroy a few nerds. Dumbasses who started with me are still there taking csc400+ lvl classes and passing. Get through the early bullshit and its pretty challenging/fun major (teacher pending).

6/14/2007 5:20:17 PM

 Message Boards » Study Hall » CSC - Extreme Programming Page [1]  
go to top | |
Admin Options : move topic | lock topic

© 2024 by The Wolf Web - All Rights Reserved.
The material located at this site is not endorsed, sponsored or provided by or on behalf of North Carolina State University.
Powered by CrazyWeb v2.39 - our disclaimer.