News for hackers. Stuff that matters.
Re:Myths of Enterprise Python by pc86 on Wednesday December 10, 2014 @03:56PM (#8731628)
> Our most common success story starts with a Java or C++ project slated to take a team of 3-5 developers somewhere between 2-6 months, and ends with a single motivated developer completing the project in 2-6 weeks (or hours, for that matter).

A story so common they did not feel the need to share it? Even taking the least ludicrous numbers I'm going to say this is entirely made up.

- 3 C++ devs, 40 hours a week for 2 months (8wks) = 960 hours

- 1 Python dev, 40 hours a week for 6 weeks = 240 hours

4x difference in productivity is not a language difference, it's a programmer skill difference.

And just for the sake of seeing the numbers:

- 5 C++ devs, 40 hours a week for 6 months (24 wks) = 4800 hours

- 1 Python dev, 40 hours a week for 2 weeks = 80 hours

= 60x productivity

No.

Re:Myths of Enterprise Python by markrwilliams on Wednesday December 10, 2014 @04:06PM (#8731690)
You're underestimating the amount of effort put into simplifying and clarifying implementations, APIs, and documentation.

This doesn't imply that preceding implementers are unskilled. Part of this improvement is hindsight, but a not-insignificant part is Python's flexibility.

I can vouch for the apparently unbelievable productivity gains but I'm just not sure how to prove them!

Edit: As for not sharing these gains -- that's part of the point of this post to the official PayPal engineering blog :)

Re:Myths of Enterprise Python by mhashemi on Wednesday December 10, 2014 @04:16PM (#8731746)
I figured 2500 words was quite enough for an introductory post. It definitely has happened, multiple times, but the rather mundane specifics will have to wait til a future post :)
Re:Myths of Enterprise Python by justin_vanw on Wednesday December 10, 2014 @05:31PM (#8732140)
I would have to agree with you, choice of language does not give a 60x productivity gain.

However, it's not crazy to think that a really top notch engineer, who is an expert in Python, and who is operating on a much healthier and efficient team would give you a 60x improvement. Heck, 60x might be too low.

It's not a priori crazy to find a 60x productivity difference between two teams. What is the productivity improvement between one team who spends 1 year on a project and fails to deliver it, vs another team that delivers the project in 4 months? It's not 3x, because 3x better than nothing is still nothing. The second team is literally infinitely more productive.