|Sent on:||Wednesday, April 17, 2013 12:45 PM|
On Apr 17, 2013, at 12:09 PM, Gloria W wrote:Yes, there are Python freelancers who take these types of jobs, based on the hourly rate and type of work, etc.
I would argue that given the current market, nothing can be deemed "stable" any more. What is commonly called a "permanent job" is usually more volatile than many contracts I have worked on, in more subversive ways than short term contracts, because the volatility is often hidden from the employee until the last minute.
Plus, looking at the lifespan of any really good developer at any company, it averages less than two years if that person has little or no ownership in the company. Those who "know what they're doing" have a constant flow of options presented to them.This has been a real eye opener for us during our current recruiting phase. One of the first things I look at when I see a resume is how long the person has averaged at their previous positions. We see a lot of resumes which list a sequence of supposedly permanent positions and average out to between 1 and 2 years at each. We saw one recently that averaged 10 months. In my mind, that's a major down-check. How can we hire somebody, expect to invest time and effort to bring them up to speed on the project (not to mention shell out a recruiter fee of several months salary), when we know they're going to leave in a year.
This message was sent by Roy Smith ([address removed]) from The New York Python Meetup Group.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
To learn more about Roy Smith, visit his/her member profile