ThoughtWorks

[ChimpMaster]

I know someone who works there. Very well paid, and a lot of respect is given to technical expertise, which is rare in most organisations. They seem to work on leading/bleeding edge tech most of the time and never work on packages (SAP/IBM etc) as far as I know.

The hippy thing is correct too

[v8gaz]

Isn't this one a Gerry Anderson puppet?

https://www.thoughtworks.com/profiles/erin-cummins

[DimPrawn]

Isn't this one a Gerry Anderson puppet?

https://www.thoughtworks.com/profiles/erin-cummins

[The Plantswoman]

I'm starting a project soon with this outfit at client co. After a couple of weeks of sitting down with them and seeing how they work. I have come to the conclusion that they are completely nuts.

They have sold client co 100% paired programming with swapping user stories and pairs every day.

As per my other thread, that is exactly the kind of thing I want to avoid like the plague.

Does pair programming mean you spend all of your time double teamed with somebody at the same desk?

[Ketto]

Is the client co in Greater Manchester by any chance?

[alreadypacked]

They tried to headhunt me a few years ago, I said NO.
The guy was a bit taken aback, "You know you are being headhunted?"
The answer is still NO.

[eek]

They tried to headhunt me a few years ago, I said NO.
The guy was a bit taken aback, "You know you are being headhunted?"
The answer is still NO.

I get that all the time... Why don't you want to work for this Tier 1 global consultancy.....

[jmo21]

Does pair programming mean you spend all of your time double teamed with somebody at the same desk?

it's definitely not supposed to be 100% of the time that's for sure!

[ChimpMaster]

They tried to headhunt me a few years ago, I said NO.
The guy was a bit taken aback, "You know you are being headhunted?"
The answer is still NO.

I thought you were a SAP consultant?

[LondonManc]

As per my other thread, that is exactly the kind of thing I want to avoid like the plague.

Does pair programming mean you spend all of your time double teamed with somebody at the same desk?

Pretty much from what I saw. One types, one proof reads as they type. It's an extension of waterfall's cost to fix versus when-detected graph - the sooner you detect something, the cheaper it is to fix it. In theory it makes your backseat driving programmer a permanent unit tester rather than an actual programmer. How much it actually reduces on test costs, I don't know, but I'd imagine that it varies between programming teams.