What does an XP team room look like?
scissor.com
What does an XP team room look like?
1–10 of 19 posts
Re: What does an XP team room look like?
#2Blech. Who works on world-changing projects and uses the vernacular of 'XP' when discussing coding environments?
Re: What does an XP team room look like?
#3"We also followed the XP practice of pair programming, which is why you'll see only two desks for the four programmers."
Pair programming is stupid. It is ok in only two situations:
A senior engineer is teaching around a more junior engineer (or somebody that just started).
There is a modification/urgent patch going on, that is touching very critical point of the application, or that is being done right before the product is shipping.
I just can't imagine good developers like pair programing. It is such a waste of resources.
Re: What does an XP team room look like?
#4Blech. Who works on world-changing projects and uses the vernacular of 'XP' when discussing coding environments?
Paid XP adoption consultants like the guy who wrote the article.
Re: What does an XP team room look like?
#5"We also followed the XP practice of pair programming, which is why you'll see only two desks for the four programmers." Pair programming is stupid. It is ok in only two situations: A senior engineer is teaching around a more junior engineer (or somebody that just started). There is a modification/urgent patch going on, that is touching very critical point of the application, or that is being done right before the pr…
I like pair programming. It's not stupid - it's counterintuitive, and like any counterintuitive idea is vulnerable to snap dismissal, as your comment appears to exemplify.
Anyone who's ever spent hours going down a rabbit hole that in retrospect was an obvious mistake may have a conception of why it's not necessarily a waste of resources. That, and anyone who realizes that programming isn't straightforward and he may not have all the best ideas about how to do something.
It's too bad that the discourse around pair programming is dominated by people who think it should be mandated and people who think it's stupid.
Re: What does an XP team room look like?
#6Just another label for a personality disorder suffered by a particular group of programmers. Nothing new to see here, move along now.
Re: What does an XP team room look like?
#71 computer and 2 guys? Their budget must be horrible, poor people can't even afford a second pair of keyboard and a mouse so they can at least use the same machine at he same time :D
Re: What does an XP team room look like?
#8I'm in two minds about this kind of thing. On the upside, some of these ideas really do seem like they could help programmers to do things quickly and with fewer bugs. On the downside, the combination of bright colours, constant supervision, hand-holding, over-planning and idiot-proofing would make me feel like some kind of cross between a kindergartener and a galley slave.
Re: What does an XP team room look like?
#9Isn't this anti-37 signals?
Ok ok , before the downmods come, I'm just saying!!! This seems to be everything that 37 signals DOES NOT stand for, so the point is ...to each his own!
Re: What does an XP team room look like?
#10"We also followed the XP practice of pair programming, which is why you'll see only two desks for the four programmers." Pair programming is stupid. It is ok in only two situations: A senior engineer is teaching around a more junior engineer (or somebody that just started). There is a modification/urgent patch going on, that is touching very critical point of the application, or that is being done right before the pr…
I like pair programming. It's not stupid - it's counterintuitive, and like any counterintuitive idea is vulnerable to snap dismissal, as your comment appears to exemplify. Anyone who's ever spent hours going down a rabbit hole that in retrospect was an obvious mistake may have a conception of why it's not necessarily a waste of resources. That, and anyone who realizes that programming isn't straightforward and he may…
Anyone who's ever spent hours going down a rabbit hole that in retrospect was an obvious mistake may have a conception of why it's not necessarily a waste of resources. That, and anyone who realizes that programming isn't straightforward and he may not have all the best ideas about how to do something.
Sure, but many people know when they are about to go down a rabbit hole, and can just ask a colleague for some advice.
Also, experience is the best teacher. If you rely on the person sitting next to you to prevent you from making mistakes, you don't learn anything.