From: Kirk Haines <wyhaines@...>
Date: 2011-05-18T21:28:32+09:00
Subject: Re: Ruby Future Or?

--00151750d9f613f2c104a38c06c0
Content-Type: text/plain; charset=ISO-8859-1

1) Yes. For some jobs, the Ruby is what is important, not the Rails.

2) I don't know because I have not been job hunting for quite a while, but I
am confident that there are. Those jobs are certainly a minority, but they
are not a fantasy.

Kirk Haines
Engine Yard
On May 17, 2011 1:37 AM, "Chad Perrin" <code@apotheon.net> wrote:
> On Tue, May 17, 2011 at 05:31:11AM +0900, Kirk Haines wrote:
>> On Mon, May 16, 2011 at 12:48 PM, Chad Perrin <code@apotheon.net> wrote:
>> >
>> > From what I've seen, Rails is a primary job skill sought by employers.
>> > Ruby without Rails, however, seems to be just a "bonus", if employers
>> > notice it at all.
>>
>> It depends. We (Engine Yard) employ several people for whom Ruby
>> related work is their daily bread and butter, but those people do not
>> spend their days writing Rails apps.
>
> I have two questions:
>
> 1. Did you hire them for their Ruby-not-Rails skills, or hire them for
> their Ruby on Rails skills and end up putting them to work with Ruby that
> is not attached to Rails?
>
> 2. Do you know of any other businesses that hire people for Ruby skills
> that aren't related to Rails and are *not* basically the Google of Ruby
> employers?
>
> Of all the job postings I've noticed that mention Ruby in job
> requirements, 100% of them also mention Rails.
>
> --
> Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]

--00151750d9f613f2c104a38c06c0--