Paul Robinson wrote: > On 20 Nov 2008, at 22:08, Rahoul Baruah wrote: > > >> Because (as Caius said) if people are looking for Ruby developers >> then I don't see a problem with workingwithrails and LinkedIn >> > > > They just don't work for employers. Go out tomorrow and try and get me > half a dozen Rails devs available for work in the North of England > immediately using those tools alone. > > WWR gives you next to nothing (too US-centric). LinkedIn requires you > to spend a year going to networking events and doesn't scale for this > job. The reality is that most employers are not prepared to do either > for a 3-month dev contract. > In my experience WWR doesn't work for freelancers either. I've had a couple of people contact me from it, but one was a recruiter (who as usual sounded really optimistic when I initially spoke to him, but I haven't heard from since), and one wanted me to be CTO of his startup in London (nice, but I've just moved back from down South).
If you're applying for any of the work posted that lets you work remotely, most of it is in the US and they get lots of applicants from places like India, China and South America who have decent CVs and charge $10-15 an hour. Which groups do people use on LinkedIn? I don't have any Ruby-related groups on my profile at present, so that's something I should remedy. > > >> - I get far >> more offers through them (and google) than I can deal with (although >> many are admittedly rubbish). >> > > > That's kind of a good example of my point: you're turning work away > and as a result the employers aren't just moving onto the next name on > the list: *they're changing frameworks*. That's bad for all of us. > > I'm glad you can find work, but that's not the only problem we're > trying to solve: it's trying to make employers realise the skills are > here and to invest. If they can't see there are plenty of Rails devs > they just won't invest in the tech and in the long run that kills all > of us off. > > I know for a fact that there are several hundred Ruby developers in > the North of England. Why then, even as somebody in the scene does it > cause me so much trouble to find *one* that is available for work? I > think once we fix that, we're flying... > Indeed. As a newcomer to the NW, the only reason I know there's any Ruby activity round here is because I already knew about NWRUG. From looking at the job boards, etc. it doesn't look like there's any Ruby work going on - lots of PHP and C#, but no Ruby. If you're an employer and none of your usual channels show anyone else looking for Ruby guys, then you'll be less willing to invest in a language or framework if you think it'll be hard to find people. I think the group meetings do help with that - Paul found out about *one* freelancer looking for work last night (and would've heard of me sooner if there'd been a meet in the past month or two ;-) - but having to wait for the next meeting isn't ideal (and we wouldn't want lots of employers turning up to try to find coders anyway :-) Adrian. -- Booklert - Track your book's rank on Amazon http://www.mcqn.com/booklert/ tedium - It's not about making lists, it's about crossing things off http://www.mcqn.com/tedium --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NWRUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nwrug-members?hl=en -~----------~----~----~----~------~----~------~--~---
