What artifact do you get when you get a massage? What artifact do you get when you go to the theatre? What about taking a class in school, what artifact (aside from books) do you get from that?
Here in Toronto, cable (Rogers/Shaw) peaks around 2-3.5 Mbits/sec... DSL here is generally half that, from my experience. A friend of mine has had lots of problems with slow speeds (peaking at ~25 kB/s), and there is extremely noticible interference on his phone line while he is connected.
Also, he's had the bell connection program crash several times, and it often displays debug messages randomly.
Two brains are better than one. You shouldent be so embarrassed of your code that you cant let another developer look at it. That's a waste of time... Everyone makes mistakes when they're coding... generally the developer you're working with should know you well enough so as not to say "You're missing a close curly" when you know very well you are... If you're working on a large project... Maybe one person has more experience with one aspect of it than another. It's a very easy and fast way to gain coding experience. When we do over-the-shoulder, justification of our methods is simple, because we both respect each other's opinions.
Maybe a conclusion that we could draw from this is that you need dedicated developers working on a project in order for XP to work correctly.
I know how your girlfriend must have felt, being on a team of incompitent programmers... From what I gather, XP is for people who actually want to use the methods discussed, and it's probably not intended for people who dont care how they code, as long as they get their deposit in the bank (IMHO). I usually find when code gets destroyed around here, it's because a lack of communication in the workplace. I can imagine how terrible it would feel to have code destroyed, and then having someone try to incorrectly justify why they did it without consulting you in the first place...
Anyway, that's just my $0.02 CAD, (roughly 0.0132 American).
A co-developer of mine here at the office has the eXtreme Programming book, and we've tried the over-the-shoulder method several times now. It's great, it gives each person a chance to add to the code, and it cuts down on the need for a code-review, but does not eliminate the need. I think it really helps us to not be "in the dark" with each other's code too.
I havent tried doing this with any of the other developers yet, but im sure the results would be just as good. I also believe it took a small chunk out of our overall coding time.
I'm intrested in hearing others have tried any other methods (I'm not very familliar(?sp) with the book myself).
Slashdot Mirror
What artifact do you get when you get a massage? What artifact do you get when you go to the theatre? What about taking a class in school, what artifact (aside from books) do you get from that?
You use the word 'customer' a few times in this comment....
From WordNet (r) 1.6 :
customer
n : someone who pays for goods or services [syn: client]
I'm just configuring some templates for a wireless printer, used for printing parking tickets by officers with handheld computers.
Here in Toronto, cable (Rogers/Shaw) peaks around 2-3.5 Mbits/sec... DSL here is generally half that, from my experience. A friend of mine has had lots of problems with slow speeds (peaking at ~25 kB/s), and there is extremely noticible interference on his phone line while he is connected.
Also, he's had the bell connection program crash several times, and it often displays debug messages randomly.
Two brains are better than one. You shouldent be so embarrassed of your code that you cant let another developer look at it. That's a waste of time... Everyone makes mistakes when they're coding... generally the developer you're working with should know you well enough so as not to say "You're missing a close curly" when you know very well you are... If you're working on a large project... Maybe one person has more experience with one aspect of it than another. It's a very easy and fast way to gain coding experience. When we do over-the-shoulder, justification of our methods is simple, because we both respect each other's opinions.
Maybe a conclusion that we could draw from this is that you need dedicated developers working on a project in order for XP to work correctly.
I know how your girlfriend must have felt, being on a team of incompitent programmers... From what I gather, XP is for people who actually want to use the methods discussed, and it's probably not intended for people who dont care how they code, as long as they get their deposit in the bank (IMHO). I usually find when code gets destroyed around here, it's because a lack of communication in the workplace. I can imagine how terrible it would feel to have code destroyed, and then having someone try to incorrectly justify why they did it without consulting you in the first place...
Anyway, that's just my $0.02 CAD, (roughly 0.0132 American).
A co-developer of mine here at the office has the eXtreme Programming book, and we've tried the over-the-shoulder method several times now. It's great, it gives each person a chance to add to the code, and it cuts down on the need for a code-review, but does not eliminate the need. I think it really helps us to not be "in the dark" with each other's code too.
I havent tried doing this with any of the other developers yet, but im sure the results would be just as good. I also believe it took a small chunk out of our overall coding time.
I'm intrested in hearing others have tried any other methods (I'm not very familliar(?sp) with the book myself).