Revised Python job survey

[Joseph Santaniello]

> | I'm not even interested in statistically accurate info. All
> | I want to be able to say is "I got 10 apparently well-qualified
> | people on comp.lang.python say they would consider moving to LA
> | for the right money."
>
> I'd also put in your survey:
>  (a) How long did it take you to learn Python, i.e.
>      to become relatively proficient.
>  (b) What language they came from (Visual Basic, Java, etc)
>  (c) If they like Python better or not.
>  (d) If they think they are more productive with Python
>  (e) If they think their software is more reliable with Python.

These are all good points, however management is already convinced of the
technical suitability to our project. They also have a hunch that we're
not kidding that Python is easy to learn. I was thinking of teaching the
main person I need to convince as part of my argument! Their only issue is
what happens if for some reason they get stuck holding the bag on a
product written in Python and need to quickly get somebody to fix
something that might get broken, and the 2 programmers who know Python
have as they say "been hit by a bus."

If I don't get succeed with demonstrating that Python folk are available,
I'll go with the "it's easy to learn" tactic.

We'll see.

Thanks,

Joseph

>
> This way you can tell your management, well I only got 20
> respondants who said they'd move to LA to code in Python.
> HOWEVER, on average, they said it took them 2 months to
> get up-to-speed and, on average, they said they feel
> more productive and are producing more reliable software!
> THEREFORE, even if we have to hire Visual Basic/Java programmers,
> it won't be all that much effort to have them learn Python.
>
> Just some thoughts,
>
> Clark
>
>
> ----- End forwarded message -----
>
>